Skip to content

fix: sync --version output and wire release-please marker#50

Merged
leonkenneth merged 1 commit into
mainfrom
fix/version-release-please-marker
Jul 13, 2026
Merged

fix: sync --version output and wire release-please marker#50
leonkenneth merged 1 commit into
mainfrom
fix/version-release-please-marker

Conversation

@leonkenneth

Copy link
Copy Markdown
Contributor

Problem

altertable --version prints the VERSION constant from cli/src/version.ts, which was hardcoded at 1.0.0. The actual released version is 1.1.0 (.release-please-manifest.json, cli/package.json), so --version reported the wrong number.

release-please-config.json lists cli/src/version.ts as a generic extra-file to bump, but the generic updater only rewrites lines carrying an x-release-please-version marker — and the line had none, so release-please never touched it.

Fix

  • Bump VERSION to 1.1.0 to match the current release.
  • Add the // x-release-please-version marker so release-please keeps it in sync on future releases.

🤖 Generated with Claude Code

VERSION was hardcoded at 1.0.0 while the released version is 1.1.0, so
`altertable --version` reported the wrong number. release-please listed
cli/src/version.ts as a generic extra-file but never updated it because
the line lacked an x-release-please-version marker.

Bump to 1.1.0 and add the marker so future releases stay in sync.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@leonkenneth leonkenneth merged commit a3e86e8 into main Jul 13, 2026
9 checks passed
@leonkenneth leonkenneth deleted the fix/version-release-please-marker branch July 13, 2026 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants