Skip to content

[JENKINS-69074] Bump to Winstone 5.27 - #6896

Closed
joaocfernandes wants to merge 1 commit into
jenkinsci:masterfrom
joaocfernandes:winstone-5.27
Closed

[JENKINS-69074] Bump to Winstone 5.27#6896
joaocfernandes wants to merge 1 commit into
jenkinsci:masterfrom
joaocfernandes:winstone-5.27

Conversation

@joaocfernandes

@joaocfernandes joaocfernandes commented Jul 21, 2022

Copy link
Copy Markdown

See JENKINS-69074.

Winstone changes: jenkinsci/winstone@winstone-5.25...winstone-5.27

Proposed changelog entries

Proposed upgrade guidelines

N/A ?

Submitter checklist

  • (If applicable) Jira issue is well described
  • Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change) and are in the imperative mood. Examples
    • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
  • Appropriate autotests or explanation to why this change has no tests
  • New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadoc, as appropriate.
  • New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO") if applicable.
  • For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@mention

Maintainer checklist

Before the changes are marked as ready-for-merge:

  • There are at least 2 approvals for the pull request and no outstanding requests for change
  • Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
  • Changelog entries in the PR title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood
  • Proper changelog labels are set so that the changelog can be generated automatically
  • If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
  • If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

* Winstone 5.27 - Update Jetty from 9.4.46.v20220331 to 9.4.48.v20220622

https://github.com/jenkinsci/winstone/releases/tag/winstone-5.27
@NotMyFault NotMyFault added dependencies Pull requests that update a dependency file proposed-for-close There is no consensus about feasibility of this PR, and maintainers do not see a way forward for it labels Jul 23, 2022
@NotMyFault

Copy link
Copy Markdown
Member

Hey,
thanks for your PR. Updating Jetty and Winstone is already done in #6801 superseding this PR.

@joaocfernandes

Copy link
Copy Markdown
Author

Hey, thanks for your PR. Updating Jetty and Winstone is already done in #6801 superseding this PR.

Thanks for your reply! I will keep tracking that PR. Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file proposed-for-close There is no consensus about feasibility of this PR, and maintainers do not see a way forward for it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants