Repository navigation
feat(registry): support verified repository renames - #209
Merged
Merged
Conversation
Registry v2 packages may list repository.previous_identities: canonical host/path identities the repository had before a forge rename. Listed identities are validated (canonical, no self-reference, no duplicates, no collision with another package's current or previous identity). The release index generator accepts previous releases and tombstones recorded under a listed identity, so lineage carries over monotonically and the next certified release moves to the new identity. For GitHub it first checks that the old and new names resolve to the same numeric repository ID; a mismatch keeps the prior release and reports certification_failed. Unlisted identity changes still fail generation. The client treats indexed releases, installed release metadata, Git checkouts, lookups and channel preferences recorded under a listed identity as the same package. Live provider candidates must still match the current identity. plugin.py regenerated with generate_plugin.py. The luxtronikex rename lands via PR #208. refs #208 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Unblocks #208 (refs #208).
Problem: A forge rename changes
repository.url, so the registry identity no longer matchesrepository_identityinrelease_index.json.generate_release_index.py --updatethen fails withPrevious release repository no longer matches registry., which blocks index refresh for every plugin.Change:
repository.previous_identities(canonicalhost/owner/repo). Validation rejects malformed entries, self-reference, duplicates, and identities already claimed by another package.certification_failed. Unlisted identity changes still fail.plugin.pyregenerated; CONTRIBUTING documents the field.Not included: the luxtronikex registry change, which lands via #208 plus
previous_identitiesafter this merges.Tests: full suite passes locally;
validate_plugins.pypasses.🤖 Generated with Claude Code