chore: resolve dependabot security alerts#225
Merged
MarshallOfSound merged 1 commit intomainfrom Apr 4, 2026
Merged
Conversation
erikian
approved these changes
Apr 4, 2026
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
2 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.
Resolves the currently open Dependabot security alerts via
yarn up -R— lockfile-only refreshes within existing semver ranges. Nopackage.jsonchanges, noresolutionsentries needed.picomatchyarn up -R(transitive, in-range)4.0.3→4.0.4taryarn up -R(transitive, in-range)7.5.10→7.5.13minimatch(9.x)yarn up -R(transitive, in-range)9.0.5→9.0.9minimatch(5.x)yarn up -R(transitive, in-range)5.1.6→5.1.9globyarn up -R(transitive, in-range)10.4.5→10.5.0js-yamlyarn up -R(transitive, in-range)4.1.0→4.1.1Incidental in-range bumps from the same refresh:
glob7.1.6→7.2.3, new[email protected]entry (pulled in by[email protected]).All picked versions satisfy the 7-day
npmMinimalAgeGate.yarn install --immutablepasses.Flagged (not changed)
None — every open alert was resolvable with an in-range lockfile refresh.
Safe-only sweep: only lockfile refreshes within existing semver ranges were applied. No direct dependency ranges were widened and no
resolutionsoverrides were added.yarn npm auditstill reports a handful of unrelated advisories (@babel/helpers,@eslint/plugin-kit,ajv,brace-expansion,yaml) that are not currently open Dependabot alerts for this repo; those were left out of scope for this PR.