fix(release): recover missed extension publication - #93
Merged
Conversation
- select an unpublished current version after a successful main gate\n- keep published extension versions as no-op
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.
Outcome\n\nA successful main gate now recovers an Extension version whose earlier publication was skipped because its upstream repository gate failed. Published versions remain no-op.\n\n## Evidence\n\n- Telegram
0.2.0is absent from the registry and selectstrue.\n- An already-published Extension version selectsfalse.\n-pdm run checkpasses: 10 passed, 50 skipped.\n\nThis keeps recovery inside the normal main-gate publication workflow; it does not misuse the initial-publication dispatch path.