Record 0.4.0 and fix the catalog fixture - #92
Merged
Merged
Conversation
Keep package, catalog, and local smoke observations with their sources.
The unpublished-candidate test mixed fake registry data with the live catalog. Give it a local fixture so a valid catalog release cannot break the test. Keep public release links accessible to all readers.
raghubetina
changed the title
raghubetina
marked this pull request as ready for review
September 23, 2026 02:29
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.
Record plugin 0.4.0 publication, package identity, catalog selection, and the local compile-and-boot smoke. Link public release notes to public evidence.
The release-order test mixed a fake unpublished registry with the repository's live catalog. After the valid 0.4.0 catalog update, it failed even though publication was correct. Give the test its own candidate and catalog fixture while retaining all release-order assertions.
Validation: all nine focused release-order tests and
git diff --checkpassed; the updated PR runs normal CI. Package contents, compatibility declarations, and protected publication controls are unchanged.