Bump pipeline-utility-steps from 2.6.1 to 2.15.3 in /jenkinsfile-runner/resources #61
Conversation
This file contains 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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [pipeline-utility-steps](https://github.com/jenkinsci/pipeline-utility-steps-plugin) from 2.6.1 to 2.15.3. - [Release notes](https://github.com/jenkinsci/pipeline-utility-steps-plugin/releases) - [Changelog](https://github.com/jenkinsci/pipeline-utility-steps-plugin/blob/master/CHANGES.md) - [Commits](jenkinsci/pipeline-utility-steps-plugin@pipeline-utility-steps-2.6.1...pipeline-utility-steps-2.15.3) --- updated-dependencies: - dependency-name: org.jenkins-ci.plugins:pipeline-utility-steps dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
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.
Bumps pipeline-utility-steps from 2.6.1 to 2.15.3.
Release notes
Sourced from pipeline-utility-steps's releases.
... (truncated)
Commits
47919a1[maven-release-plugin] prepare release pipeline-utility-steps-2.15.30ba4f32[SECURITY-2196]8e8289e[maven-release-plugin] prepare for next development iteration100c2e2[maven-release-plugin] prepare release pipeline-utility-steps-2.15.209a6ec2Merge pull request #209 from jenkinsci/dependabot/maven/io.jenkins.tools.bom-...ea64d2aMerge pull request #208 from jenkinsci/dependabot/maven/org.jenkins-ci.plugin...a7a9b72Bump bom-2.361.x from 2000.v4677a_6e0ffea to 2025.v816d28f1e04f424c34eBump plugin from 4.59 to 4.6170283dbMerge pull request #207 from jenkinsci/dependabot/maven/io.jenkins.tools.bom-...bd3086cBump bom-2.361.x from 1981.v17df70e84a_a_1 to 2000.v4677a_6e0ffeaDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.