fix: make D1 post-apply audit compatible with Wrangler - #4210
Merged
Merged
Conversation
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.
Summary
wrangler d1 migrations list --jsonpost-apply audit path with the supported text-output pathNo migrations to apply!) is present--json/|| trueand keep the audit after applyProduction evidence
Post-merge D1 Migrate run #11 (
36901437326) reached production with:List pending migrations: success,No migrations to apply!Apply migrations: success,No migrations to apply!Confirm no migrations remain pending (audit log): failure because Wrangler 4.144.0 rejects--jsonA direct read-only D1 check after the run still shows 46 applied migrations through
0051_add_tt_phase_round_reported_results.sql, matching the 46 top-level migration SQL files on main; pending remains 0.Safety boundary
This PR changes
.github/workflows/d1-migrate.yml, so merging it tomainwill trigger another production D1 migration workflow run. Keep this PR draft until that second production run is explicitly intended.No migration SQL, dependency/lockfile, Cloudflare credential/environment, D1 target, or application behavior changes.
Refs #3476