release: track target version 0.8.0 in changelog and packages - #48
Merged
Conversation
- CHANGELOG.md: pending section is now '## [0.8.0] - Unreleased' — the accumulating release names the version it will become instead of a bare [Unreleased] stamped at publish time. - Bump @altananetwork/sdk and @altananetwork/mcp to 0.8.0 (features this cycle -> pre-1.0 minor); mcp's sdk range follows; lockfile refreshed. - CONTRIBUTING.md: codify the version logic — first user-visible change of a cycle creates the section and bumps versions (fix -> patch, feature -> minor), target only ever goes up within a cycle; publish = stamp the date, verify versions, npm publish, merge staging -> main. - PR template checkbox updated to match.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What & why
The changelog's pending section now names the version it will become:
## [0.8.0] - Unreleased(features this cycle → pre-1.0 minor bump).@altananetwork/sdkand@altananetwork/mcpare bumped to 0.8.0 to match (mcp's sdk dependency range follows; lockfile refreshed).The rule is now part of the flow (CONTRIBUTING.md + PR template): the first user-visible change of a cycle creates the section and bumps versions — fix starts a patch, feature starts a minor, and the target only ever goes up within a cycle. Publishing is then just: stamp the date, verify versions match, npm publish, merge staging → main.
Once this merges to staging it rides the open promotion PR #47 automatically, so main receives the changelog already versioned.
How was this tested?
bun install(lockfile refresh) — version metadata only, no code changes.Anything breaking?
No.