fix: replace standard-version with inline release versioning#48
Merged
Conversation
The release workflow now determines the next version from git tags directly, avoiding conflicts with existing tags. Removes standard-version dependency. https://claude.ai/code/session_01HNvBcQzT1SviRqkUpP5Xce
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
2 participants
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.
Summary
standard-versionwith inline git-tag-based versioning in the release workflowstandard-versiondevDependencyContext
After ejecting projen (#47), the release workflow used
standard-versionwhich tried to create tagv0.0.1(bumping from package.json's0.0.0), but that tag already existed. The new approach reads the latest tag (e.g.v0.0.47) and increments from there.Test plan
npm run buildpasses locallyhttps://claude.ai/code/session_01HNvBcQzT1SviRqkUpP5Xce