Skip to content

fix: end a staging run in dry-run mode so semantic-release never tags it - #5

Merged
Mearman merged 1 commit into
mainfrom
fix/staging-never-tags
Oct 10, 2026
Merged

Mearman merged 1 commit into
mainfrom
fix/staging-never-tags

Conversation

@Mearman

@Mearman Mearman commented Oct 10, 2026

Copy link
Copy Markdown
Member

semantic-release tags and pushes right after prepare, so every staging run created and pushed the release tag before the pull request merged. The next staging run then failed on "tag already exists", and the publish job's own tag step would have too. prepare now sets dryRun, which the core reads after prepare to skip tag, push and publish plugins. The publish job keeps ownership of the tag.

semantic-release tags and pushes the release straight after prepare. For a staged release that
tag names a commit which is not on the base branch, and the next staging run fails with
"tag already exists". Setting dryRun from prepare makes the core skip the tag, the push and every
publish plugin, leaving tagging to whatever publishes after the pull request merges.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
🔒 Security Review ✅ Completed 2026-10-10T15:25:24.641236Z f28aeaa Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Mearman

Mearman commented Oct 10, 2026

Copy link
Copy Markdown
Member Author

@codex security review

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review

Security review completed. No security issues were found in this pull request.

Reviewed commit: f28aeaa8dc

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ 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.

@Mearman
Mearman merged commit 6a53140 into main Oct 10, 2026
7 checks passed
@Mearman
Mearman deleted the fix/staging-never-tags branch October 10, 2026 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant