Repository navigation
Fixed release tag landing on wrong commit and wrong version number - #47
Merged
oleg68 merged 1 commit intoApr 14, 2026
Merged
Conversation
Previously the tag was created before the CHANGELOG auto-edit commit, so: 1. "git tag --points-at HEAD" in Calculate version found nothing (HEAD had advanced to the CHANGELOG commit), causing RELEASE=OFF and the release to be skipped entirely. 2. The tag name did not match the commit count from the previous tag, since the CHANGELOG commit adds one more commit on top of HEAD. Fix: commit CHANGELOG first, then tag HEAD (+1 to account for the new commit), then push both. FULL_VER is now recomputed with +1 inside the release branch so the patch number stays consistent. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
oleg68
added a commit
to oleg68/NetbeansPluginClaudeCodeGui
that referenced
this pull request
Apr 14, 2026
…bplugins#47) Previously the tag was created before the CHANGELOG auto-edit commit, so: 1. "git tag --points-at HEAD" in Calculate version found nothing (HEAD had advanced to the CHANGELOG commit), causing RELEASE=OFF and the release to be skipped entirely. 2. The tag name did not match the commit count from the previous tag, since the CHANGELOG commit adds one more commit on top of HEAD. Fix: commit CHANGELOG first, then tag HEAD (+1 to account for the new commit), then push both. FULL_VER is now recomputed with +1 inside the release branch so the patch number stays consistent. Co-authored-by: Oleg Samarin <osamarin@openintegration.inc> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
oleg68
added a commit
that referenced
this pull request
Apr 15, 2026
…) (#49) Previously the tag was created before the CHANGELOG auto-edit commit, so: 1. "git tag --points-at HEAD" in Calculate version found nothing (HEAD had advanced to the CHANGELOG commit), causing RELEASE=OFF and the release to be skipped entirely. 2. The tag name did not match the commit count from the previous tag, since the CHANGELOG commit adds one more commit on top of HEAD. Fix: commit CHANGELOG first, then tag HEAD (+1 to account for the new commit), then push both. FULL_VER is now recomputed with +1 inside the release branch so the patch number stays consistent. Co-authored-by: Oleg Samarin <osamarin@openintegration.inc> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
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
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.
Previously the tag was created before the CHANGELOG auto-edit commit, so:
Fix: commit CHANGELOG first, then tag HEAD (+1 to account for the new commit), then push both. FULL_VER is now recomputed with +1 inside the release branch so the patch number stays consistent.