fix(ci): push release commit and tags to remote#65
Merged
markusnissl merged 1 commit intomainfrom Apr 6, 2026
Merged
Conversation
Two release workflow fixes: 1. Add 'git push --follow-tags' after nx release — NX only commits and tags locally, it does not push to the remote. 2. Run 'go mod tidy' in updateProjectDependencies after go.mod version bumps. Without this, go.sum has stale checksums that don't match the updated dependency versions in go.mod.
markusnissl
force-pushed
the
fix/release-push-tags
branch
from
3cad4fa to
443c5c9
Compare
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.
NX Release only stages, commits, and tags locally. It does not push to the remote. This is why no tags appeared on GitHub after triggering the release workflow.
Adds
git push --follow-tagsafternx releaseto push both:httpx/v1.5.0,security/netutil/v1.2.0)