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

[branch-2.10][improve][build] Upgrade dependencies to reduce CVE. #20162

Merged
merged 3 commits into from
Apr 22, 2023

Conversation

Technoboy-
Copy link
Contributor

@Technoboy- Technoboy- commented Apr 21, 2023

Motivation

Upgrade the jetty server version to avoid CVE-2023-26048
Upgrade kotlin version to avoid CVE-2022-24329

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

@Technoboy- Technoboy- changed the title [improve][build] Upgrade dependencies to reduce CVE. [branch-2.10][improve][build] Upgrade dependencies to reduce CVE. Apr 21, 2023
@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Apr 21, 2023
@codelipenghui
Copy link
Contributor

Do we need to update the notice file?

@Technoboy-
Copy link
Contributor Author

Do we need to update the notice file?

yes, updated

@codelipenghui
Copy link
Contributor

/pulsarbot run-failure-checks

@lhotari
Copy link
Member

lhotari commented Jun 2, 2023

@Technoboy- Please don't do this type of PRs that aren't in the master branch. Maintenance will be a mess if we continue with this type of approach. Each dependency (or group of related dependencies) should be upgraded separately as well. We don't want these PRs that are bundles of multiple commits. If you want to trigger the CI tests, that can be achieved by manually triggering the pipeline in GitHub Actions UI. It's probably not supported in all maintenance branches at the moment. In those cases, it's possible to use a PR that isn't merged and is only for triggering the tests.

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

Successfully merging this pull request may close these issues.

None yet

4 participants