fix(registry): preserve published pet manifests#32
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.
Root cause
The 0.2.2 Pet Studio release added
pet.custom.manageby tightening the existingconvax.plugin/5Pet rule from three capabilities to four. Registry Pages revalidates every immutable published Release, so the valid 0.2.1 entry was rejected before the new catalog could be rebuilt.Fix
pet.custom.managecapability as the only optional fourth Pet grantRegression coverage
plugin-convax-pet-v0.2.1/registry-entry.jsonparses with the repaired validatorbun run checkpasses: all workspace builds, typechecks, tests, companion builds, validation, deterministic packing, Registry, and Showcase generation