build(dev-deps): bump js-yaml and @babel/core to patch security advis…#2066
Merged
Conversation
…ories Updates transitive dev dependencies to their patched versions to resolve open Dependabot alerts (all dev-scope, lockfile only): - js-yaml 4.1.1 -> 4.3.0 (alert #101, GHSA-h67p-54hq-rp68) - js-yaml 3.14.2 -> 3.15.0 nested under @istanbuljs/load-nyc-config (alert #102) - @babel/core 7.29.0 -> 7.29.7 and babel family (alert #99, GHSA-4x5r-pxfx-6jf8) All patched versions satisfy existing semver ranges; package.json unchanged. npm audit reports 0 vulnerabilities; build, 126 tests, and lint all pass.
graikhel-intel
approved these changes
Jun 30, 2026
|
🎉 This PR is included in version 5.0.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
…ories
PR Checklist
What are you changing?
Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. device-management-toolkit/repo#365 )