Repository navigation
fix: keep v0.2.18 bytes for request-log provider migration - #31
Merged
Merged
Conversation
v0.2.19 retabbed 006_request_log_provider.sql, so databases that already applied it panic on boot with a checksum mismatch. Restore the original SQL and accept the tab-indented checksum so existing stores can start.
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.
Summary
006_request_log_provider.sqlbytes from v0.2.18.v0.2.19 retabbed an already-applied migration. us1 panic-looped on
migration 006_request_log_provider.sql checksum mismatchand the updater rolled back to v0.2.18.Test plan
go test ./internal/accounts/ -count=1release.ymlfrommainto publish v0.2.20, then upgrade us1 from the console.