-
Notifications
You must be signed in to change notification settings - Fork 54
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
chore(DGHT-287): Fix Dependabot alerts #5463
Conversation
Storybook for this PR deployed on this github page |
@@ -1,4 +1,4 @@ | |||
import { rest } from 'msw'; | |||
import { http, HttpResponse, } from 'msw'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest
renamed to http
, and use HttpResponse
to replace res
parameter
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran npm script on-msw-upgrade
to regenerate service worker file after msw
upgraded.
'@talend/react-cmf': minor | ||
'@talend/scripts-publish-local': patch | ||
'@talend/scripts-locales': patch | ||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For packages with major dependency upgrade, I use a minor changeset.
For packages with patch dependency upgrade, I use a patch changeset.
@@ -1,4 +1,4 @@ | |||
import { rest } from 'msw'; | |||
import { http, HttpResponse, } from 'msw'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe remove the extra ,
"path-to-regexp": "^3.3.0", | ||
"path-to-regexp": "^8.2.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
be sure you have tested an existing CMF application with the router 🙏
There are unit test that should be good but we never know.
By the way there are still a 6.0 in the lock file, so the security issue will stay. Do you know where it comes from ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the comment!
I checked playground and vite-playground which works fine.
version 6 comes from multiple packages but 6.3.0 is a "safe" version :
=> Found "[email protected]"
info Has been hoisted to "path-to-regexp"
info Reasons this module exists
- "workspace-aggregator-8113ffd5-c4b4-4412-9f5c-5bcfa979cb8e" depends on it
- Hoisted from "_project_#@talend#ui-playground-vite#vite-plugin-mock#path-to-regexp"
- Hoisted from "_project_#@talend#react-containers#msw#path-to-regexp"
- Hoisted from "_project_#@talend#react-bootstrap#sinon#nise#path-to-regexp"
What is the problem this PR is trying to solve?
Resolve Dependabot alerts in the project.
This PR will fix:
https://github.com/Talend/ui/security/dependabot/242
https://github.com/Talend/ui/security/dependabot/241
https://github.com/Talend/ui/security/dependabot/237
https://github.com/Talend/ui/security/dependabot/216
https://github.com/Talend/ui/security/dependabot/215
https://github.com/Talend/ui/security/dependabot/245
Dependencies upgraded:
"cross-spawn": "^7.0.3" => "^7.0.6"
"path-to-regexp": "^3.30" => "^8.2.0"
"msw": "^1.3.5" => "^2.6.6"
"msw-storybook-addon": "^1.10.0" => "^2.0.4"
"browser-sync": "^2.29.3" => "^3.0.3"
Changes:
path-to-regexp
in matchPath.js. Test passed after change.msw
in AboutDialog container's story and storybook configuration. Regenerate msw service worker. Storybook of react-containers package works fine after this change.msw-storybook-addon
need to be upgraded from 1.x to 2.x because we upgraded msw.Changeset:
For packages with major dependency upgrade, I use a minor changeset.
For packages with patch dependency upgrade, I use a patch changeset.
What is the chosen solution to this problem?
Please check if the PR fulfills these requirements
yarn changeset
to a request a release from the CI if wanted.[ ] This PR introduces a breaking change