ci: migrate from semantic-release to release-please#79
Merged
Conversation
Adopt the same release flow as Aonyx-bom: release-please drives versioning via conventional commits, and a tag-triggered workflow publishes the JARs to the OneLiteFeather Maven repository.
Mirror the Aonyx-bom approach: release-please updates the version in gradle.properties through the `x-release-please-version` marker, so the publish pipeline can rely on the project version baked into the repo.
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
1 participant
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
Adopts the same release flow as Aonyx-bom: release-please drives versioning via Conventional Commits, the version is maintained in
gradle.propertiesvia thex-release-please-versionmarker, and a tag-triggered workflow publishes the JARs.Added
release-please-config.json—release-type: simple,include-v-in-tag: true, packagebutterfly,extra-files: ["gradle.properties"].release-please-manifest.json— bootstrap at1.0.23(last released tag).github/workflows/release-please.yaml— runs on push tomain.github/workflows/publish.yaml— runs onv*tag push, builds and publishes to the OneLiteFeather Maven repoChanged
gradle.properties— version now1.0.23 # x-release-please-version, so release-please syncs the project version into the repo on every release PRRemoved
.releaserc.json.github/workflows/sematic-releases.ymlpackage.json,package-lock.json(no more npm-based release tooling)Follow-up (manual, GitHub UI)
The release workflow only triggers on
main. Once this PR is merged intonext:maintonext(Settings → Branches).next→main(which retires the legacymain).developand the obsoleteclaude/add-release-please-RcrsW.legacy/main-2025-07as a safety net for the oldmainstate.Test plan
mainand confirm release-please opens a release PR.v*tag is created.Publish JARworkflow runs on the tag and uploads to the OneLiteFeather Maven repo.Generated by Claude Code