chore(workflows): Setup auto-merge workflows for safe dependencies updates and BOM updates.#41
Merged
jonesbusy merged 1 commit intojenkinsci:mainfrom Jan 24, 2026
Conversation
…dates and BOM updates.
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.
Hello
pipeline-lib-orasdevelopers! 👋This is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:
Setup auto-merge workflows
io.jenkins.tools.pluginmodernizer.AutoMergeWorkflows
Setup auto-merge workflows
Setup the auto-merge workflows from Jenkins plugin archetype for safe dependencies updates (like parent pom or extensions).
Workflows either merge or close the PRs depending on the dependency.
Why is this important?
Reduce maintenance burden and noise in automatic PRs by auto-merging safe dependency updates.
Closing BOM update PRs will ensure that the plugin depends on minimum plugins version for the given Jenkins baseline.
Bumping the BOM version is only required when the plugin needs a newer version of a plugin dependency.
See Archetype for more details.