-
Notifications
You must be signed in to change notification settings - Fork 915
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
[CVE] Bump tsd
to 0.21.0
#1770
[CVE] Bump tsd
to 0.21.0
#1770
Conversation
which removes dependency chain: - `update-notifier` - `latest-version` - `package-json` - `got` Signed-off-by: Josh Romero <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #1770 +/- ##
=======================================
Coverage 67.50% 67.51%
=======================================
Files 3073 3073
Lines 59068 59069 +1
Branches 8963 8963
=======================================
+ Hits 39876 39879 +3
+ Misses 17008 17007 -1
+ Partials 2184 2183 -1
Continue to review full report at Codecov.
|
See #1369 for an example of all of the details that should be included in a CVE PR, including adding a link to the changelog and calling out any breaking changes there. |
Updated in PR description; will copy to commit message when merging. |
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.
Are we targeting v2.1?
If we can, I think that'd be best? Or are you saying that this may need to wait? |
Do we see this causing conflicts with plugins? If just for testing purposes at least under OpenSearch Project they use Cypress. |
I would imagine this affects more than tests - in the dashboards core, we use |
I did a bit more digging. I see no evidence that any of the internal packages updated by this PR are used in any other repo (either in the org or in GitHub globally). Unless there's some non-standard mechanism I'm not aware of for plugins to take explicit dependencies on these packages, this shouldn't cause any conflicts. org searches for each of the packages getting a
(As a side note, it appears we chose not to update the package name from I also did an org search for any other explicit |
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.
LGTM! I'll defer to your decision if to backport or not. I don't see a particular issue with backporting to 2.x for 2.1.
If you do, can you add the v2.1.0
label.
Thanks!
- Partially addresses: CVE-2022-33987 - bumps `tsd` dependencies from `0.16.0` to `0.21.0` (latest) - [`tsd` release changelog](https://github.com/SamVerschueren/tsd/releases) - Breaking changes: - `0.17.0` includes "Require Node.js 12" - this is not a breaking change as we've already update to node `14.19.1` `tsd v0.17.0` removes dependency chain: - `update-notifier` - `latest-version` - `package-json` - `got` Partial fix for #1764 Signed-off-by: Josh Romero <[email protected]> (cherry picked from commit d1cfe78)
- Partially addresses: CVE-2022-33987 - bumps `tsd` dependencies from `0.16.0` to `0.21.0` (latest) - [`tsd` release changelog](https://github.com/SamVerschueren/tsd/releases) - Breaking changes: - `0.17.0` includes "Require Node.js 12" - this is not a breaking change as we've already update to node `14.19.1` `tsd v0.17.0` removes dependency chain: - `update-notifier` - `latest-version` - `package-json` - `got` Partial fix for #1764 Signed-off-by: Josh Romero <[email protected]> (cherry picked from commit d1cfe78) Co-authored-by: Josh Romero <[email protected]>
Description
tsd
dependencies from0.16.0
to0.21.0
(latest)0.17.0
includes "Require Node.js 12" - this is not a breaking change as we've already update to node14.19.1
tsd v0.17.0
removes dependency chain:update-notifier
latest-version
package-json
got
Issues Resolved
Partial fix for #1764
Check List
yarn test:jest
yarn test:jest_integration
yarn test:ftr