chore(plugins): gate registry script in CI, drop completed migration script#1385
Merged
Conversation
…to-v2 migration script
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.
What
Cleanup of the two stray Python files found in a repo audit:
test_update_registry.pyinto CI. The test existed but nothing ran it. It now runs once in theresolve-tagsjob (before any plugin builds), so the registry prune logic (drops nullpluginKitVersionbinaries, keeps the two newest) is guarded on every plugin release/dispatch.scripts/migrate-registry-v1-to-v2.py. Its own docstring marks it a one-time v1-to-v2 migration. The live registry is alreadyschemaVersion: 2, so the migration is done and the script is dead.Not touched
update-registry.pystays (active, used bybuild-plugin.yml).No app code, no user-facing strings.