Skip to content

chore: switch to a stable 0.1.0 release line and pin the 0.x major - #157

Merged
OmarAlJarrah merged 1 commit into
mainfrom
chore/version-0.1.0
Jul 20, 2026
Merged

chore: switch to a stable 0.1.0 release line and pin the 0.x major#157
OmarAlJarrah merged 1 commit into
mainfrom
chore/version-0.1.0

Conversation

@OmarAlJarrah

Copy link
Copy Markdown
Member

Summary

Graduates kuri out of the 0.1.0-alpha.N prerelease series onto a stable 0.x line, and configures release automation so the major digit stays at 0 until a deliberate 1.0.0.

  • Version state. gradle.properties and .release-please-manifest.json now record 0.1.0 (was 0.1.0-alpha.4).

  • Release config. Removes the prerelease settings from release-please-config.json (prerelease, prerelease-type, versioning), so release-please cuts plain 0.y.z releases instead of advancing an alpha counter. The pre-major settings are kept and are what pins the line at 0.y.z:

    • bump-minor-pre-major → breaking changes bump the minor (0.1.00.2.0), never 1.0.0.
    • bump-patch-for-minor-pre-majorfeat and fix bump the patch (0.1.00.1.1).

    The automation therefore never crosses to 1.0.0 on its own; reaching 1.0.0 is a deliberate manual Release-As: 1.0.0.

  • Docs. README install snippets, coordinate table, Kuri.VERSION example and the 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. Kuri.kt's version KDoc example is updated.

Publishing note

0.1.0 has 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 the v0.1.0 tag 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:

Closes #94
Closes #99

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.
@OmarAlJarrah
OmarAlJarrah merged commit 1955651 into main Jul 20, 2026
11 of 13 checks passed
@OmarAlJarrah
OmarAlJarrah deleted the chore/version-0.1.0 branch July 20, 2026 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant