Repository navigation
fix(migrations): renumber zero-Skill repo clear to 0127 - #311
Merged
Merged
Conversation
Collaborator
Author
🤖 READY · 100/100
|
harlan-zw
added
the
harlan-agent-ready
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
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.
❓ Type of change
📚 Description
#309 and #308 both added a migration numbered 0126, and #309 merged first. The migration-naming test now fails on main, so the deploy for #308 was skipped (Test run).
Production already applied
0126_resync_skilld_cache_skill_repos.sql(deploy run), so it keeps its number.0126_clear_broken_zero_skill_repos.sqlnever ran, so it moves to 0127 with its SQL unchanged. The UPDATE is idempotent either way.