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

[Task]: Update Java BOM dependencies #28379

Closed
1 of 15 tasks
lostluck opened this issue Sep 8, 2023 · 3 comments · Fixed by #28656
Closed
1 of 15 tasks

[Task]: Update Java BOM dependencies #28379

lostluck opened this issue Sep 8, 2023 · 3 comments · Fixed by #28656
Assignees

Comments

@lostluck
Copy link
Contributor

lostluck commented Sep 8, 2023

What needs to happen?

Follow
https://cwiki.apache.org/confluence/display/BEAM/Dependency+Upgrades to update Java Bom dependencies prior to the release cut, if necessary. If unsure, ask the dev list for assistance or an opinion.

Then move the milestone to the next release.

Issue Priority

Priority: 2

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@kennknowles
Copy link
Member

The BOM had a minor version update last week. It is pretty high risk to make the change right before the release. I think this should really be post-release-branch-cut work so we have some time to stabilize. I'll ask around about any vital fixes included.

@kennknowles
Copy link
Member

@kennknowles
Copy link
Member

I am moving this to the next milestone since we need to get 2.51.0 out the door and I am not aware of critical vulnerabilities. I will get it updated on master concurrently with the release, and it can have time to bake. If anyone is aware of a critical vulnerability, please raise it.

@kennknowles kennknowles self-assigned this Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants