Fix vulerability issues #85
Merged
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
BREAKING CHANGE: Update several packages to latest major.
alexcanessa
had a problem deploying
to
staging
GitHub Actions
Failure
✅ Deploy Preview for commercelayer-sanity-template ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
alexcanessa
had a problem deploying
to
staging
GitHub Actions
Failure
alexcanessa
force-pushed
the
fix-vulerability-issues
branch
from
cc3542c
to
765647f
Compare
f-picca
approved these changes
Feb 13, 2024
alexcanessa
force-pushed
the
fix-vulerability-issues
branch
from
765647f
to
77e8bcc
Compare
alexcanessa
force-pushed
the
fix-vulerability-issues
branch
from
77e8bcc
to
2c87e67
Compare
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.
What I did
This PR is to resolve vulnerability issues spotted by our dependabot, majority of which were a matter of upgrading packages to their latest version.
Upgrading meant changing some code, which is also part of this PR.
Naturally, it's a breaking change, added to the relevant commit.
Two unrelated changes are a fix to the linting script; a fix to getting the token from the Cookies and I've applied formatting rules and committed changed files.
How to test
Clone the repo and follow the README.md files. Unfortunately, I couldn't check the integration with Commerce Layer itself, but I'm confident the code works.
Checklist