Skip to content

fix: correct release-please manifest to bootstrap at v1.0.0#47

Merged
ddulic merged 1 commit intomainfrom
003-github-releases
Mar 16, 2026
Merged

fix: correct release-please manifest to bootstrap at v1.0.0#47
ddulic merged 1 commit intomainfrom
003-github-releases

Conversation

@ddulic
Copy link
Copy Markdown
Owner

@ddulic ddulic commented Mar 16, 2026

Summary

  • Set .release-please-manifest.json to {"." : "0.14.8"} (actual last version) so release-please has a correct baseline
  • Remove initial-version from config (manifest drives versioning now)
  • Add feat!: bootstrap commit to trigger a major bump from 0.14.81.0.0

The previous run created PR #46 proposing 0.1.0 because the empty manifest caused release-please to start from 0.0.0 and bump via feat: commits. With the manifest set correctly and a breaking change commit, the next release-please PR will propose 1.0.0.

Bootstrap release-please manifest from 0.14.8. The breaking change
marker triggers a major version bump to 1.0.0 as the first formal
GitHub release.

BREAKING CHANGE: first public stable release
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@ddulic ddulic merged commit 6afd7ac into main Mar 16, 2026
5 checks passed
@ddulic ddulic deleted the 003-github-releases branch March 16, 2026 11:52
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.

1 participant