chore: migrate from semantic-release to release-please #2339
Conversation
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
dkhawk
approved these changes
Dec 15, 2025
kikoso
force-pushed
the
chore/migrate-to-release-please
branch
from
944e036 to
84df05a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Migrate the repository from
semantic-releasetorelease-pleaseto simplify release management.. This change introduces a "Release PR" strategy where releases are prepared in a PR and published upon merge.Changes
semantic-releaseconfiguration (.releaserc) and the old .github/workflows/release.yml.release-pleaseconfiguration files:android-sampleswithsimplerelease type and Gradle file updates.1.19.0.googleapis/release-please-action@v4.ApiDemos-java-debug.apk,ApiDemos-kotlin-debug.apk) when a release is created.Effect
On the next merge to main,
release-pleasewill search for Conventional Commits and open a "Release PR" if changes are found. Merging that PR will create a GitHub Release, tag the commit, and upload the built APKs.