Bump org.jenkins-ci.main:jenkins-core from 2.547 to 2.549#1192
Bump org.jenkins-ci.main:jenkins-core from 2.547 to 2.549#1192dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [org.jenkins-ci.main:jenkins-core](https://github.com/jenkinsci/jenkins) from 2.547 to 2.549. - [Release notes](https://github.com/jenkinsci/jenkins/releases) - [Commits](jenkinsci/jenkins@jenkins-2.547...jenkins-2.549) --- updated-dependencies: - dependency-name: org.jenkins-ci.main:jenkins-core dependency-version: '2.549' dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
☀️ Quality MonitorTests Coverage for New Code 〰️ Line Coverage (Changed Code): n/a (0 missed lines) Coverage for Whole Project 〰️ Line Coverage (Whole Project): 87.50% (102 missed lines) Style Bugs API Problems🚫 Revapi (Whole Project): No warnings Vulnerabilities🛡️ OWASP Dependency Check (Whole Project): 226 vulnerabilities (error: 17, high: 61, normal: 141, low: 7) Software Metrics 🌀 Cyclomatic Complexity (Whole Project): 318 (total) 🚦 Quality GatesOverall Status: ✅ SUCCESS✅ Passed Gates
Created by Quality Monitor v4.0.0 (#8f591a4). More details are shown in the GitHub Checks Result. |
Bumps org.jenkins-ci.main:jenkins-core from 2.547 to 2.549.
Commits
8fb447e[maven-release-plugin] prepare release jenkins-2.549f72718bDo not run symlink tests on Windows if symlinks are not supported (#26203)4a7abf9Update stapler.version to v2072 (major) (#26242)f21b5bdUpdate dependency commons-codec:commons-codec to v1.21.0 (#26221)587f636Update dependency org.jenkins-ci.main:jenkins-test-harness to v2553 (#26239)a9fa26aUpdate dependency globals to v17.3.0 (#26238)6c7d282Update babel monorepo to v7.29.0 (#26237)6910edfFix shutdown banner visibility on Plugin Manager pages (#26234)b1da869Update dependency stylelint to v17.1.0 (#26232)213efedUpdate dependency com.puppycrawl.tools:checkstyle to v13.1.0 (#26236)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)