Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require Jenkins 2.440.3 or newer #1144

Merged
merged 1 commit into from
Jun 11, 2024

Conversation

MarkEWaite
Copy link
Contributor

@MarkEWaite MarkEWaite commented Jun 8, 2024

Require Jenkins 2.440.3 or newer

Plugin installation statistics show that 76% of all installations of git client plugin 4.7.0 are already running Jenkins 2.440.3 or newer.

SECURITY-3386 security advisory requires Jenkins 2.440.3 or newer to avoid CVE-2023-48795.

Choosing a Jenkins version recommends either 2.426.3 or 2.440.3. In this case, I think that 2.440.3 is the better choice.

@olamy and @jtnord I would appreciate your input on this pull request. I think this is the right time to increase the minimum required Jenkins version for the git client plugin so that a narrower range of Jenkins core versions are supported.

Checklist

  • I have read the CONTRIBUTING doc
  • I have referenced the Jira issue related to my changes in one or more commit messages
  • I have added tests that verify my changes
  • Unit tests pass locally with my changes
  • I have added documentation as necessary
  • No Javadoc warnings were introduced with my changes
  • No spotbugs warnings were introduced with my changes
  • I have interactively tested my changes

Types of changes

What types of changes does your code introduce?

  • Maintenance

https://stats.jenkins.io/pluginversions/git-client.html shows that 76%
of all installations of git client plugin 4.7.0 are already running
Jenkins 2.440.3 or newer.

https://www.jenkins.io/security/advisory/2024-04-17/#SECURITY-3386
security advisory requires Jenkins 2.440.3 or newer to avoid
https://www.cve.org/CVERecord?id=CVE-2023-48795
@MarkEWaite MarkEWaite added the chore Reduces maintenance effort by changes not directly visible to users label Jun 8, 2024
@MarkEWaite MarkEWaite requested a review from a team as a code owner June 8, 2024 10:30
@MarkEWaite MarkEWaite merged commit d4b5aec into jenkinsci:master Jun 11, 2024
15 checks passed
@MarkEWaite MarkEWaite deleted the require-2.440.3-or-newer branch June 11, 2024 02:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Reduces maintenance effort by changes not directly visible to users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants