Bump org.jenkins-ci.plugins:plugin from 5.18 to 5.28 #514
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
Bumps [org.jenkins-ci.plugins:plugin](https://github.com/jenkinsci/plugin-pom) from 5.18 to 5.28. - [Release notes](https://github.com/jenkinsci/plugin-pom/releases) - [Changelog](https://github.com/jenkinsci/plugin-pom/blob/master/CHANGELOG.md) - [Commits](jenkinsci/plugin-pom@plugin-5.18...plugin-5.28) --- updated-dependencies: - dependency-name: org.jenkins-ci.plugins:plugin dependency-version: '5.28' dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
dependabot
bot
added
dependencies
|
@jenkinsci/gitlab-branch-source-plugin-developers/@timja , could someone please merge and release this parent bump in a new version? We have a few PCTs failing whose fix is in a updated Apologies for the direct ping |
1 task
Member
|
@jetersen perhaps? |
MarkEWaite
added a commit
to MarkEWaite/gitlab-branch-source-plugin
that referenced
this pull request
Nov 16, 2025
Java 25 released September 16, 2025. The Jenkins project wants to support Java 25 soon. Compile and test on ci.jenkins.io with Java 25 and Java 21. Intentionally continues to generate Java 17 byte code as configured by the plugin parent pom. Does not compile or test with Java 17 on ci.jenkins.io any longer because we have found no issues in the past that were specific to the Java 17 compiler. The plan is to drop support for Java 17 in the not too distant future so that the Jenkins project is only supporting two major Java versions at a time, Java 21 and Java 25. Simplifies the configuration block of the Jenkinsfile so that it more closely resembles the Jenkins plugin archetype. Requires pull requests: * jenkinsci#514 * jenkinsci#510 * jenkinsci#506 Testing done: * Confirmed that automated tests pass with Java 25
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 org.jenkins-ci.plugins:plugin from 5.18 to 5.28.
Release notes
Sourced from org.jenkins-ci.plugins:plugin's releases.
... (truncated)
Commits
7a07196[maven-release-plugin] prepare release plugin-5.282c07fb0Update dependency org.jenkins-ci.main:jenkins-test-harness to v2519 (#1245)ce9a28dUpdate dependency org.apache.maven.plugins:maven-war-plugin to v3.5.0 (#1244)073bf8fUpdate dependency org.jenkins-ci.main:jenkins-test-harness to v2516 (#1243)aa6c5a3Update dependency org.jenkins-ci.main:jenkins-test-harness to v2513 (#1242)d79625cUpdate dependency com.palantir.javaformat:palantir-java-format to v2.81.0 (#1...a8b203aUpdate dependency org.apache.maven.plugins:maven-antrun-plugin to v3.2.0 (#1240)6f27afcUpdate dependency com.github.spotbugs:spotbugs-maven-plugin to v4.9.8.1 (#1239)4d791ebre-enable requirePluginVersions (#1124)6bf83f8Update dependency com.github.spotbugs:spotbugs-maven-plugin to v4.9.8.0 (#1238)Dependabot 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)