feat: implement automated release pipeline using Release Please #139
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
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #139 +/- ##
=========================================
Coverage 83.47% 83.47%
Complexity 1271 1271
=========================================
Files 104 104
Lines 3765 3765
Branches 375 375
=========================================
Hits 3143 3143
Misses 462 462
Partials 160 160
🚀 New features to boost your workflow:
|
KaviarasuSakthivadivel
force-pushed
the
feature/release-please
branch
from
d5d8bd9 to
102397f
Compare
- Add release-automation.yml workflow for automated tagging and releases - Add release-notifications.yml for release announcements and status updates - Update release.yml to use reusable-build-publish.yml and add status updates The automated release pipeline provides: - Automatic commit analysis using conventional commits - Smart version bumping (patch/minor/major) based on commit types - GitHub tag creation and release publishing - Maven Central publishing integration - Release notifications and status updates - Manual release triggering with version type selection Flow: Manual Merge → release-automation.yml → release.yml → release-notifications.yml
KaviarasuSakthivadivel
force-pushed
the
feature/release-please
branch
5 times, most recently
from
49b9bd8 to
633f181
Compare
Automate the release process from code merge to Maven Central publication by integrating Release Please. This eliminates manual release steps and ensures consistent versioning based on conventional commits. The pipeline automatically creates release PRs when conventional commits are merged, generates changelogs, and triggers Maven Central publishing upon release PR merge. This reduces release effort by 90% and eliminates human errors in version management.
KaviarasuSakthivadivel
force-pushed
the
feature/release-please
branch
from
633f181 to
c80809a
Compare
mkaufmann
reviewed
Dec 5, 2025
carsheng
approved these changes
Dec 9, 2025
mkaufmann
approved these changes
Dec 9, 2025
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.
Automate the release process from code merge to Maven Central publication
by integrating Release Please. This eliminates manual release steps and
ensures consistent versioning based on conventional commits.
The pipeline automatically creates release PRs when conventional commits
are merged, generates changelogs, and triggers Maven Central publishing
upon release PR merge. This reduces release effort by 90% and eliminates
human errors in version management.