Skip to content

fix(release): push release commit and tags after they are created - #37568

Open
cestercian wants to merge 1 commit into
nrwl:masterfrom
cestercian:fix/release-push-after-commit
Open

cestercian wants to merge 1 commit into
nrwl:masterfrom
cestercian:fix/release-push-after-commit

Conversation

@cestercian

@cestercian cestercian commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Current Behavior

With release.git.push: true and no createRelease, nx release pushes right after versioning while the changes are only staged (the version step falls back to git.push), and then never pushes again after committing and tagging. So the release commit and tags never reach the remote.

Expected Behavior

releaseVersion is called with gitPush: false, and nx release pushes once after commit and tag when git.push is enabled (or --git-push is passed), or when a remote release is configured like before. --no-git-push and dry run still work. Added release.spec.ts covering the push order and the push disabled case.

Related Issue(s)

Fixes #37427

@netlify

netlify Bot commented Oct 22, 2026

Copy link
Copy Markdown

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 3c600b4

@netlify

netlify Bot commented Oct 22, 2026

Copy link
Copy Markdown

👷 Deploy request for nx-dev pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 3c600b4

@cestercian
cestercian requested a review from a team as a code owner October 22, 2026 15:31
@cestercian
cestercian requested a review from lourw October 22, 2026 15:31

This branch has not been deployed

No deployments
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.

nx release pushes before committing and tagging when git.push is true without createRelease

1 participant