Repository navigation
Run CI on the published release commit without moving version aliases - #32
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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 current release workflow successfully publishes a metadata commit and exact tag using GITHUB_TOKEN. GitHub intentionally suppresses push-triggered workflows for these pushes, so the latest release/main commit has no check runs even though its parent passed Jira E2E.
After successful publication, validate the tag target and explicitly dispatch the existing unit/static/native-action/Jira E2E workflows against the immutable tag. Add manual triggers to those existing workflows. The dispatcher alone receives actions:write; dispatched tests retain their existing permissions. Dispatch-triggered E2E cannot start another release because the publisher requires a main push event.
Replace the legacy technote-space tag workflow (a second publisher with mutable alias/rebuild behavior) with read-only verification of the exact tag, commit, package version, packaged entry point and published notes. The existing release workflow remains the publication owner. Existing version tags and aliases are not changed.
Evidence: current latest release commits return zero check runs. GitHub documents that workflow_dispatch can trigger runs with GITHUB_TOKEN while ordinary push events do not. YAML parses locally. Current-head CI, actual dispatch execution, and the resulting release-commit checks must pass before this repair is complete.