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

[Dependencies] Upgrade Werkzeug from version 2.0.* to version 3.0.3 #6370

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

gmarciani
Copy link
Contributor

Description of changes

Upgrade Werkzeug from version 2.0.* to version 3.0.3 to address vulnerability https://github.com/aws/aws-parallelcluster/security/dependabot/9.

Tests

  • PR checks

References

  • Link to impacted open issues.
  • Link to related PRs in other packages (i.e. cookbook, node).
  • Link to documentation useful to understand the changes.

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@gmarciani gmarciani added skip-changelog-update Disables the check that enforces changelog updates in PRs dependencies Pull requests that update a dependency file 3.x labels Jul 26, 2024
Signed-off-by: Giacomo Marciani <mgiacomo@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.x dependencies Pull requests that update a dependency file skip-changelog-update Disables the check that enforces changelog updates in PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant