[PROD] Bump webpack from 5.78.0 to 5.94.0 in /frontend #2348
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [webpack](https://github.com/webpack/webpack) from 5.78.0 to 5.94.0. - [Release notes](https://github.com/webpack/webpack/releases) - [Commits](webpack/webpack@v5.78.0...v5.94.0) --- updated-dependencies: - dependency-name: webpack dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
…bpack-5.94.0 Bump webpack from 5.78.0 to 5.94.0 in /frontend
kryswisnaskas
requested review from
Jones-QuarteyDana
and removed request for
Jones-QuarteyDana
AdamAdHocTeam
approved these changes
Sep 3, 2024
|
Merging this, since it unblocks PR #2347 which was already approved for deployment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
Bumps webpack from 5.78.0 to 5.94.0 in /frontend and updates known vulnerabilities for the frontend.
This change is needed for PR #2347 to be successfully deployed
How to test
Make sure all tests pass
Issue(s)
Checklists
Every PR
Before merge to main
Production Deploy
After merge/deploy