Skip to content

[Fix CVE-2025-47273]Bump setuptools to 78.1.1 #3671

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

Merged
merged 1 commit into from
May 27, 2025

Conversation

RyanL1997
Copy link
Contributor

Description

[Fix CVE-2025-47273]Bump setuptools to 78.1.1

Related Issues

Check List

  • New functionality includes testing.
  • New functionality has been documented.
  • New functionality has javadoc added.
  • New functionality has a user manual doc added.
  • API changes companion pull request created.
  • Commits are signed per the DCO using --signoff.
  • Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Copy link
Collaborator

@noCharger noCharger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RyanL1997 do we need backport?

@RyanL1997
Copy link
Contributor Author

We can back to 2.19 + 1.3 just in case we have a patch release, cuz eventually it is impacted all of our branches


SQL: OpenSearch Plugin 
origin/main 
origin/3.0 
origin/2.x 
origin/2.19 
origin/2.18 
origin/2.0 
origin/1.2 
origin/1.1 
origin/1.0 
JDBC-2.0.0.0 
3.0.0.0 
2.19.2.0 
2.19.1.0 
2.19.0.0 
2.18.0.0 
2.4.0.0 
2.3.0.0 
2.2.1.0 
2.2.0.0 
2.1.0.0 
2.0.1.0 
2.0.0.0 
1.3.6.0 
1.3.5.0 
1.3.4.0 
1.3.3.0 
1.3.2.0 
1.3.1.0 
1.3.0.0 
1.2.4.0 
1.2.3.0 
1.2.2.0 
1.2.1.0 
1.2.0.0 
1.1.0.1 
1.1.0.0 
1.0.0.0 

@Swiddis Swiddis merged commit 58696ee into opensearch-project:main May 27, 2025
24 checks passed
@opensearch-trigger-bot
Copy link
Contributor

The backport to 1.3 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/sql/backport-1.3 1.3
# Navigate to the new working tree
pushd ../.worktrees/sql/backport-1.3
# Create a new branch
git switch --create backport/backport-3671-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 58696ee3d83313ac680929d9288a26059477b033
# Push it to GitHub
git push --set-upstream origin backport/backport-3671-to-1.3
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/sql/backport-1.3

Then, create a pull request where the base branch is 1.3 and the compare/head branch is backport/backport-3671-to-1.3.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.19 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/sql/backport-2.19 2.19
# Navigate to the new working tree
pushd ../.worktrees/sql/backport-2.19
# Create a new branch
git switch --create backport/backport-3671-to-2.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 58696ee3d83313ac680929d9288a26059477b033
# Push it to GitHub
git push --set-upstream origin backport/backport-3671-to-2.19
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/sql/backport-2.19

Then, create a pull request where the base branch is 2.19 and the compare/head branch is backport/backport-3671-to-2.19.

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.

4 participants