Repository navigation
fix(ci): qualify isolated extension release writers - #973
Merged
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
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.
The release-writer contract failed after the VS Code and Continue workflows merged because it did not classify the new Continue writer. It also missed VS Code publication delegated to Python, and changes to either extension workflow did not trigger the contract on pull requests.
This change inventories both writers and preserves their separate tag namespaces. Tests execute the actual pre-publication tag guards against matching, cross-component, standard-release, wrong-version and malformed tags; assert the qualification/source-check dependencies; and require the contract to run whenever those workflows, source guards or version manifests change. Existing standard-release ownership assertions remain intact.
Validation: the original inventory failure was reproduced; all 60 recovery contract tests pass; actionlint and YAML parsing pass. All 99 adjacent recovery, coordinator, literal workflow-sequence and mutation-probe tests pass using the repository's hash-pinned Python dependencies and zipsign 0.2.1; no skips. Independent peer review found no blocking issues. No published tag, asset or release workflow is changed.
Refs #972; Gitea terraphim/terraphim-ai#3488.
Scanner comparison: no new critical or warning findings. Existing test helper eval() triggers two rules and five older subprocess tests have no timeout; baseline and final findings match. No scanner suppression or hook bypass was added.