Migrate to Maven CI-friendly versions - #249
Merged
Merged
Conversation
aziemchawdhary-gs
marked this pull request as draft
April 16, 2026 11:10
Replace hardcoded version across all 11 POMs with ${revision}, add
flatten-maven-plugin, and rewrite release workflows to use -Drevision=
instead of maven-release-plugin. This eliminates the two-commit
release dance, tag-checkout rebuild, and force-push recovery flow.
aziemchawdhary-gs
force-pushed
the
ci-friendly
branch
from
July 17, 2026 17:46
ebd52f4 to
31d9453
Compare
aziemchawdhary-gs
marked this pull request as ready for review
July 17, 2026 17:47
rafaelbey
approved these changes
Jul 17, 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
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.
Replace hardcoded version across all 11 POMs with ${revision}, add flatten-maven-plugin, and rewrite release workflows to use -Drevision= instead of maven-release-plugin. This eliminates the two-commit release dance, tag-checkout rebuild, and force-push recovery flow.