chore: resolve open dependabot security alerts#579
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
devcycle-mcp-server | b812ec0 | Jul 23 2026, 01:50 PM |
There was a problem hiding this comment.
Pull request overview
Updates JavaScript dependencies and Yarn resolutions/lockfile entries to address multiple Dependabot security alerts in the DevCycle CLI.
Changes:
- Bump
axiosto^1.18.0(and align related Yarnresolutions/ lockfile). - Bump
js-yamlto4.2.0and add a Yarn resolution for transitive consumers. - Update Yarn
resolutions(and lockfile) forbrace-expansionandbody-parserto patched versions.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Updates direct dependencies and adds/adjusts Yarn resolutions to force patched transitive versions. |
| yarn.lock | Regenerates lock entries to reflect the updated versions and resolution outcomes. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+217
to
+218
| "body-parser@npm:^2.2.1": "^2.3.0", | ||
| "js-yaml@npm:^4.1.0": "^4.2.0" |
Member
Author
There was a problem hiding this comment.
Fixed in b812ec0: changed the direct dependency from the exact pin js-yaml: 4.2.0 to the range js-yaml: ^4.2.0. Now both the direct dep and the js-yaml@npm:^4.1.0 resolution use ^4.2.0, so Yarn deduplicates them to a single 4.3.0 instance — no two-version tree.
JamieSinn
approved these changes
Jul 22, 2026
jonathannorris
enabled auto-merge (squash)
July 23, 2026 13:50
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
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.
Summary
axiosfrom^1.15.2to^1.18.0to resolve 6 CVEs (alerts feat: Add search params to variable and feature commands #265-Log error if login port is in use #269, #272; medium/high severity)js-yamlfrom exact pin4.1.1to range^4.2.0and added a^4.1.0resolution mapping to^4.2.0to cover transitive consumers (alert feat: Add pagination flags to variable list and get commands #264; medium) — both now resolve to a single 4.3.0 instancebrace-expansion@npm:^5.0.5resolution^5.0.7to fix the 5.x vulnerable range (alert feat: add dvc identity get command #270; high — DoS via exponential-time expansion)body-parser@npm:^2.2.1resolution^2.3.0to fix transitive dep viaexpress(alert #271; low)sigstorehigh) is not resolved: the vulnerablesigstore@1.9.0is a transitive devDep (oclif -> yeoman-generator -> pacote@15.2.0 -> sigstore@^1.3.0) and no patched 1.x version exists; the only fix would be a major-version bump to 4.x which breaks pacote@15.2.0