fix: add -DallowMajorUpdates=false to lifecycle plugin version update workflow - #13186
Merged
gnodet merged 1 commit intoSep 18, 2026
Merged
Conversation
Contributor
|
@gnodet Please assign appropriate label to PR according to the type of change. |
6 tasks
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.
The
update-lifecycle-pluginsworkflow was missing-DallowMajorUpdates=false, causingversions:update-propertiesto propose major version bumps (e.g. 3.x → 4.x betas) for lifecycle plugins. This resulted in PR #13185 proposing 4.x versions for clean, compiler, deploy, install, jar, plugin, resources, and site plugins, which was not intended.Adding
-DallowMajorUpdates=falserestricts the update to minor/patch releases only, keeping lifecycle plugins on their current major version.