ci: allow release/sea/mirror to be re-run manually via workflow_dispatch - #24
Conversation
A push-triggered run whose release/sea/mirror jobs never dispatched (a GitHub Actions scheduling outage) or partially failed had no way to re-run those jobs against the already-published release without an unrelated new commit. workflow_dispatch lets it be re-triggered by hand; the three jobs' own event-name guards now accept it alongside push.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
Security findingsAdvisory findings (1)ℹ️ 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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
🛡️ Codex Security Review · Automatically triggered
Here are some automated security review suggestions for this pull request.
Reviewed commit: 5b2dbfb350
ℹ️ About Codex security reviews in GitHub
This is an experimental Codex feature. Security reviews are triggered when:
- You comment "@codex security review"
- A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review
Once complete, Codex will leave suggestions, or a comment if no findings are found.
| name: Mirror to GitHub Packages | ||
| needs: release | ||
| if: github.event_name == 'push' && github.ref == 'refs/heads/main' | ||
| if: (github.event_name == 'push' || github.event_name == 'workflow_dispatch') && github.ref == 'refs/heads/main' |
There was a problem hiding this comment.
🛡️ Codex Security Review · Automatically triggered
If a collaborator can create the latest release and dispatch main, this condition now lets them invoke the mirror without landing a commit. The job then resolves that mutable release, checks out its tag, and runs tag-controlled install/build code while NODE_AUTH_TOKEN has packages: write; release-derived values are also interpolated into shell. The collaborator can publish a malicious GitHub Packages version or exfiltrate the token, bypassing main review. Bind downstream jobs to a release output verified as an ancestor of main, pass values through env, and expose the token only at publish.
Useful? React with 👍 / 👎.
|
🎉 This PR is included in version 1.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
1 participant
GitHub Actions has been failing to dispatch jobs for the post-merge run of #23 (queued with zero jobs for 15+ minutes, well past normal scheduling delay, unrelated to this repo's own config or concurrency settings). There's currently no way to re-run release/sea/mirror-github-packages against the already-published release without pushing an unrelated commit. Adds workflow_dispatch and widens those three jobs' event-name guards to accept it alongside push.