-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Updated js-yaml to v4 #190678
Updated js-yaml to v4 #190678
Conversation
/ci |
4 similar comments
/ci |
/ci |
/ci |
/ci |
cc25199
to
c6c985a
Compare
/ci |
1 similar comment
/ci |
@elasticmachine merge upstream |
/ci |
1 similar comment
/ci |
yarn.lock
Outdated
@@ -21676,7 +21676,7 @@ js-yaml@4.1.0, js-yaml@^4.1.0: | |||
dependencies: | |||
argparse "^2.0.1" | |||
|
|||
js-yaml@^3.13.1, js-yaml@^3.14.1: | |||
js-yaml@^3.13.1: |
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.
This is coming from @istanbuljs/load-nyc-config
, we can also set a resolution, though seems negligible for now.
"**/@istanbuljs/load-nyc-config/**/js-yaml": "4.1.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.
I agree. As this is a transitive development dependency, I think it is ok to leave this for now.
Pinging @elastic/kibana-security (Team:Security) |
3cab99a
to
46dc19c
Compare
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: |
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!
## Summary Main seems to be broken because of a check. These are probably regenerated with a different shape since the js-yaml update: #190678
## Summary Since js-yaml update has been merged in #190678 we don't need `no_unsafe_js_yaml ` anymore
Summary
Updated
js-yaml
to4.1.0
.This PR also introduces a type override for the
js-yaml
load function to maintain compatibility across the codebase. Specifically, updated type definition of the load function looks as follows:The original type definition of the load function in
js-yaml
changed fromany
tounknown
. This change would require extensive type updates throughout the entire repository to accommodate theunknown
type. To avoid widespread type changes and potential issues in the codebase, the type is overriden back toany
for now.This is a temporary measure, we plan to address the necessary type changes in subsequent PRs, where teams will gradually update the codebase to work with the
unknown
type.Checklist
Release note
Updated
js-yaml
to4.1.0
.