chore: switch to a stable 0.1.0 release line and pin the 0.x major - #157
Merged
Conversation
Graduate the project out of the alpha prerelease series onto a stable 0.x line. gradle.properties and the release-please manifest now record 0.1.0, and release-please's prerelease settings (prerelease / prerelease-type / versioning) are removed so it cuts plain 0.y.z releases from here on. The pre-major bump settings are kept and are now the mechanism that holds the line at 0.y.z: bump-minor-pre-major routes breaking changes to a minor bump (0.1.0 -> 0.2.0) rather than 1.0.0, and bump-patch-for-minor-pre-major routes feat/fix to a patch bump. The major digit therefore never advances on its own; reaching 1.0.0 stays a deliberate manual Release-As step. Documentation is brought in line with the switch: the README install snippets, coordinate table, Kuri.VERSION example and stability note now read 0.1.0 and describe the 0.x series rather than an alpha one; RELEASING.md replaces the alpha-cadence and initial-alpha-publish sections with the 0.x cadence, the 1.0.0 graduation path, and a generic "bootstrap a version with no prior tag" runbook; and Kuri.kt's version KDoc example is updated. Because 0.1.0 has no prior tag, it must be published once via the manual publish workflow_dispatch (which creates the v0.1.0 tag and Release), after which merging release-please's release PRs publishes automatically.
This was referenced Jul 20, 2026
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
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
Graduates kuri out of the
0.1.0-alpha.Nprerelease series onto a stable0.xline, and configures release automation so the major digit stays at0until a deliberate1.0.0.Version state.
gradle.propertiesand.release-please-manifest.jsonnow record0.1.0(was0.1.0-alpha.4).Release config. Removes the prerelease settings from
release-please-config.json(prerelease,prerelease-type,versioning), so release-please cuts plain0.y.zreleases instead of advancing an alpha counter. The pre-major settings are kept and are what pins the line at0.y.z:bump-minor-pre-major→ breaking changes bump the minor (0.1.0→0.2.0), never1.0.0.bump-patch-for-minor-pre-major→featandfixbump the patch (0.1.0→0.1.1).The automation therefore never crosses to
1.0.0on its own; reaching1.0.0is a deliberate manualRelease-As: 1.0.0.Docs. README install snippets, coordinate table,
Kuri.VERSIONexample and the stability note now read0.1.0and describe the0.xseries rather than an alpha one. RELEASING.md replaces the alpha-cadence and initial-alpha-publish sections with the0.xcadence, the1.0.0graduation path, and a generic "bootstrap a version with no prior tag" runbook.Kuri.kt's version KDoc example is updated.Publishing note
0.1.0has no prior git tag, so — exactly like the first alpha did — it must be published once via the manual Actions → Publish → Run workflow dispatch (which creates thev0.1.0tag and GitHub Release). After that, merging release-please's release PRs publishes automatically.This change is intentionally a
chore:so graduating the version does not itself trigger a release-please bump.Supersedes
Folds in and replaces two open docs PRs, whose changes are incorporated here retargeted to
0.1.0:0.1.0.Closes #94
Closes #99