fix: reconcile Store catalog 14 with published Dictation 0.2.3 - #5
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
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.
Store catalog 13 advertises Dictation 0.2.2, while the already-published Package Index catalog 13 contains 0.2.3. Advance Store discovery to sequence 14 and match that version without rewriting either published catalog 13 or its BOM.
Local candidate validation verifies the historical signature and requires a sequence advance for changed bytes; production strict byte verification remains unchanged. Record the published Package Index catalog/BOM digests in the reconciliation fixture.
Validation:
bun run checkPASS (15 tests and strict ephemeral signing dry-run); independent Luna review PASS. Production signing/publication must use the existing Publish catalog workflow; this PR does not contain a locally generated production signature.