Bump brace-expansion and 4 dev dependencies#3891
Draft
navntoft wants to merge 2 commits into
Draft
Conversation
Bumps the following to their latest patched versions: brace-expansion (under readdir-glob): 2.0.2 → 2.1.0 picomatch (under micromatch): 2.3.1 → 2.3.2 picomatch (top level): 4.0.3 → 4.0.4 flatted: 3.3.3 → 3.4.2 js-yaml (under supertap): 3.14.1 → 3.14.2 The brace-expansion bump requires removing the brace-expansion override in package.json, which had been pinning resolution below the existing ^2.0.1 constraint declared by readdir-glob.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s npm dependency resolution to pick up newer patch/minor releases for brace-expansion (runtime, via readdir-glob) and several dev-only transitive dependencies, with corresponding lockfile updates.
Changes:
- Updated
package-lock.jsonto resolvebrace-expansion(viareaddir-glob) to2.1.0, and bumpedflatted,picomatch(both the hoisted andmicromatch-nested copies), andjs-yaml(viasupertap). - Removed the now-unnecessary
overridespin forbrace-expansion@2.0.1 -> 2.0.2frompackage.json. - Updated generated
lib/*artifacts reflecting the new dependency tree.
Show a summary per file
| File | Description |
|---|---|
| package.json | Removes a no-longer-needed overrides entry related to brace-expansion. |
| package-lock.json | Captures updated resolved versions/integrity for the bumped dependencies. |
| lib/upload-sarif-action-post.js | Generated output updated due to dependency bump (not reviewed as source). |
| lib/start-proxy-action-post.js | Generated output updated due to dependency bump (not reviewed as source). |
| lib/init-action-post.js | Generated output updated due to dependency bump (not reviewed as source). |
| lib/analyze-action-post.js | Generated output updated due to dependency bump (not reviewed as source). |
Copilot's findings
- Files reviewed: 1/6 changed files
- Comments generated: 0
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.
Bumps the following transitive dependencies:
brace-expansion(underreaddir-glob)picomatch(undermicromatch)picomatch(top level)flattedjs-yaml(undersupertap)Compatibility
I reviewed the upstream changelogs / commit logs for each transition:
brace-expansion2.0.2 → 2.1.0: no API changes. One behavior change —{1..2..0}-style zero-step inputs no longer hang — doesn't affectarchiver's glob usage.picomatch2.3.1 → 2.3.2 and 4.0.3 → 4.0.4: patch-only releases, no API changes.flatted3.3.3 → 3.4.2:parse()rewritten from recursion to iterative worklist; public signature unchanged.js-yaml3.14.1 → 3.14.2: backport-only release on the 3.x line, no API changes.Risk assessment
Low risk. Lockfile-level dependency resolution change. Build passes.
Which use cases does this change impact?
Workflow types: none specifically — applies to all.
Products: none specifically.
Environments: Testing/None — this is a build-tooling change; only
brace-expansionis in runtime scope (transitive viaarchiver).How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
archiver's zip handling (the only runtime path that touchesbrace-expansion).Are there any special considerations for merging or releasing this change?
Merge / deployment checklist
UNRELEASEDsection already reads "No user facing changes.")