fix: correct legacy AI SDK Zod peers - #17
Merged
Merged
Conversation
gcharang
added a commit
that referenced
this pull request
Jul 28, 2026
Deployment 09d99cf6 restored version b7890ecc at 2026-07-28T02:54:56Z; /health.commit reads `local` again. Production D1 was never modified, which is the correct state for the restored code. Rolled back rather than rolling forward with the migration: the displaced version had no /health verification and no attended proof behind it, so it was an unrecorded state, not a passed gate. Returning to a known baseline lets Phase 1b run in the specified order. The rollback does not fix the cause. Workers Builds still deploys non-production branches, so the next push to any branch redeploys production. Metamind PR #17 is held unmerged for that reason. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
gcharang
added a commit
that referenced
this pull request
Jul 28, 2026
Metamind PR #17 merged to dev at fb6a7b70 with CI green. Records the incident remediation as closed, with the verification rather than just the assertion: after disabling non-production branch builds, a push to the branch produced no deployment record, left /health.commit at `local`, and — the direct signal — no longer shows a `Workers Builds` check on the pull request, which the causing push did. Production remains on the documented baseline. Phase 1b is unstarted and its ordering constraint stands: the additive lease migration lands BEFORE the promotion to master, because the promotion is the deploy. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace broad peer-warning suppressions with exact-version peer overrides that explicitly support Zod 3 and Zod 4. Regenerate the lockfile so pnpm peers check reports the effective compatibility accurately.\n\nVerified:\n- pnpm peers check\n- pnpm peers check --lockfile-only\n- connector typecheck\n- connector tests (29 passed)