Fix: Release drafter uses auto-calculated next version instead of package.json#198
Merged
Fix: Release drafter uses auto-calculated next version instead of package.json#198
Conversation
Co-authored-by: wallstop <1045249+wallstop@users.noreply.github.com>
…e trailing whitespace Co-authored-by: wallstop <1045249+wallstop@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix version tag not updating to latest unreleased version
Fix: Release drafter uses auto-calculated next version instead of package.json
Feb 7, 2026
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.
Description
Release drafter was creating drafts tagged with the current
package.jsonversion (3.1.8) instead of calculating the next version from PR labels. Workflow explicitly overrode release-drafter's version resolution by passingversionandtagparameters from package.json.Changes:
versionandtagparameters to enable automatic version calculationrelease_drafter.outputs.tag_nameinstead of package.json[Unreleased]section when calculated version not yet in CHANGELOGBefore: Draft release tagged as 3.1.8 (current version)
After: Draft release tagged as 3.1.9 (next version, calculated from git tags + PR labels)
Net change: -5 lines
Type of Change
Checklist
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.