Skip to content

fix: use proper semver in release-please manifest and move major tag#108

Merged
opzkit-auto-merge[bot] merged 1 commit intomainfrom
fix/release-please-semver
Mar 11, 2026
Merged

fix: use proper semver in release-please manifest and move major tag#108
opzkit-auto-merge[bot] merged 1 commit intomainfrom
fix/release-please-semver

Conversation

@argoyle
Copy link
Copy Markdown
Member

@argoyle argoyle commented Mar 11, 2026

Summary

  • Fix version in .release-please-manifest.json from "1.0" to "1.0.0" (proper semver)
  • Add step to release-please workflow to move the major version tag (vX) on each release for GitHub Actions compatibility

Test plan

  • Pre-commit hooks pass
  • Verify release-please PR is created after merge
  • Verify major version tag is moved on next release

🤖 Generated with Claude Code

Change version from "1.0" to "1.0.0" to comply with semantic
versioning required by release-please. Also add a step to move
the major version tag (vX) on each release for GitHub Actions
compatibility.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@argoyle argoyle requested a review from peter-svensson as a code owner March 11, 2026 08:10
@opzkit-auto-merge opzkit-auto-merge Bot enabled auto-merge (squash) March 11, 2026 08:10
@opzkit-auto-merge opzkit-auto-merge Bot merged commit 517a5dd into main Mar 11, 2026
4 checks passed
@opzkit-auto-merge opzkit-auto-merge Bot deleted the fix/release-please-semver branch March 11, 2026 08:12
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