Skip to content

build(deps-dev): bump the npm_and_yarn group across 1 directory with 3 updates - #9

Closed
cldmv-bot[bot] wants to merge 2 commits into
hotfixesfrom
hotfix-redirect/pr-8
Closed

build(deps-dev): bump the npm_and_yarn group across 1 directory with 3 updates#9
cldmv-bot[bot] wants to merge 2 commits into
hotfixesfrom
hotfix-redirect/pr-8

Conversation

@cldmv-bot

@cldmv-bot cldmv-bot Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Supersedes #8. Cherry-picked cleanly onto hotfixes' own tip instead of merging Dependabot's branch as-is — that branch forks from next, and merging it directly would carry forward any of next's pooled work that isn't on hotfixes yet. See Auto-redirected PR base: on #8.


Bumps the npm_and_yarn group with 3 updates in the / directory: brace-expansion, js-yaml and minimatch.

Updates brace-expansion from 1.1.12 to 1.1.18

Release notes

Sourced from brace-expansion's releases.

v1.1.15

  • Backport v5.0.6 change to v1 (#111) 0b09384

juliangruber/brace-expansion@v1.1.14...v1.1.15

Commits

Updates js-yaml from 4.1.0 to 4.3.1

Changelog

Sourced from js-yaml's changelog.

4.3.1 - 2026-07-31

Security

  • [backport] Remove quadratic complexity from !!omap duplicate key detection.

4.3.0 - 2026-06-27

Added

  • [backport] Added maxTotalMergeKeys (10000) loader option to limit the total number of keys processed by YAML merge (<<) across one load() / loadAll() call.

Fixed

  • Restore umd builds back to es5.

Removed

  • [backport] maxMergeSeqLength replaced with maxTotalMergeKeys for limiting YAML merge processing.

[4.2.0] - 2026-06-01

Added

  • Added docs/safety.md with notes about processing untrusted YAML.
  • Added maxDepth (100) loader option. Not a problem, but gives a better exception instead of RangeError on stack overflow.
  • Added maxMergeSeqLength (20) loader option. Not a problem after merge fix, but an additional restriction for safety.
  • Added sourcemaps to dist/ builds.

Changed

  • Stop resolving numbers with underscores as numeric scalars, #627.
  • Switched dev toolchains to Vite / neostandard.
  • Updated demo.
  • Reorganized tests.
  • dist/ files are no longer kept in the repository.

Fixed

  • Fix parsing of properties on the first implicit block mapping key, #62.
  • Fix trailing whitespace handling when folding flow scalar lines, #307.
  • Reject top-level block scalars without content indentation, #280.
  • Ensure numbers survive round-trip, #737.
  • Fix test coverage for issue #221.
  • Fix flow scalar trailing whitespace folding, #307.
  • Fix digits in YAML named tag handles.

Security

  • Fix potential DoS via quadratic complexity in merge - deduplicate repeated elements (makes sense for malformed files > 10K).

[3.14.2] - 2025-11-15

Security

... (truncated)

Commits
  • 86e91b8 4.3.1 released
  • c3cc4b0 Backport quadratic complexity fix for !!omap
  • 33d05b5 4.3.0 released
  • 663bfab Drop demo publish, to not override new v5 one.
  • 1cb8c7b Add v4-legacy tag for publish
  • 02f27af Restore umd builds back to es5
  • 8be84ed Fix es5 compatibility
  • 59423c6 Replace maxMergeSeqLength option with maxTotalMergeKeys (more robust). Ba...
  • 6842ef6 doc polish
  • 590dbab 4.2.0 released
  • Additional commits viewable in compare view

Updates minimatch from 3.1.2 to 3.1.5

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

…3 updates

Bumps the npm_and_yarn group with 3 updates in the / directory: [brace-expansion](https://github.com/juliangruber/brace-expansion), [js-yaml](https://github.com/nodeca/js-yaml) and [minimatch](https://github.com/isaacs/minimatch).

Updates `brace-expansion` from 1.1.12 to 1.1.18
- [Release notes](https://github.com/juliangruber/brace-expansion/releases)
- [Commits](https://github.com/juliangruber/brace-expansion/commits)

Updates `js-yaml` from 4.1.0 to 4.3.1
- [Changelog](https://github.com/nodeca/js-yaml/blob/4.3.1/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.1.0...4.3.1)

Updates `minimatch` from 3.1.2 to 3.1.5
- [Changelog](https://github.com/isaacs/minimatch/blob/main/changelog.md)
- [Commits](isaacs/minimatch@v3.1.2...v3.1.5)

---
updated-dependencies:
- dependency-name: brace-expansion
  dependency-version: 1.1.18
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: js-yaml
  dependency-version: 4.3.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: minimatch
  dependency-version: 3.1.5
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
(cherry picked from commit 16369d4)
@cldmv-bot cldmv-bot Bot added dependencies type: dependencies Relates to dependency updates, version bumps, or package management labels Aug 3, 2026
Shinrai added a commit that referenced this pull request Aug 9, 2026
Resolves the two pre-existing high-severity transitives on next:
- picomatch 2.3.1 → 2.3.2 (via fast-glob → micromatch; runtime reach)
  fixes GHSA-3v7f-55p6-f55p (method injection) + GHSA-c2c7-rcm5-vvqj (ReDoS)
- nanoid 3.3.16 → 3.3.18 (via vitest → vite → postcss; dev)
  fixes GHSA-2v37-7h3g-55p8 (zero-size infinite loop)

Both in-range (lockfile-only, no package.json change), npm audit now
clean (0 vulnerabilities), npm ci verified, full suite green (17/17).

Folds in the intent of #9 (security transitive bumps): next already
carries newer brace-expansion (5.0.9) / minimatch (10.2.6) than #9's
targets and no js-yaml in-tree, so #9 is moot against next — its fixes
ride this release rather than the hotfixes lane.
@Shinrai

Shinrai commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Folding this into the next → master release (#20) rather than the hotfixes lane, since a patch release is already going out.

Checked against next: it already carries newer versions than this PR's targets — brace-expansion 5.0.9 (> 1.1.18), minimatch 10.2.6 (> 3.1.5), and no js-yaml in the dependency tree. So there's nothing left to apply from this PR against next; its security intent is already satisfied and will reach master when the release merges. #20 additionally patches the two transitives that were still open on next (picomatch 2.3.1 → 2.3.2, nanoid 3.3.16 → 3.3.18). Closing as superseded by the release.

@Shinrai Shinrai closed this Aug 9, 2026
Shinrai added a commit that referenced this pull request Aug 10, 2026
## Summary

Consolidates the outstanding `next`-targeting dependency work into a
single PR so it all rides the `next → master` release
([#19](#19)) together, and wires
the repo's lint/format scripts for the post-merge autofix.

### Dependency bumps (each was CI-green individually on `next`)

| Dep | Range | Role |
|---|---|---|
| `espree` | 9 → **11.2.0** | runtime (AST parser) |
| `eslint` | 9 → **10.8.1** | dev (lint) |
| `@eslint/json` | 0.13 → **2.0.1** | dev (lint) |
| `@mdn/browser-compat-data` | 6 → **8.0.10** | dev (feature data) |

### Security (transitive, lockfile-only)

| Dep | Bump | Advisory |
|---|---|---|
| `picomatch` | 2.3.1 → **2.3.2** (via `fast-glob` → `micromatch`;
**runtime reach**) | GHSA-3v7f-55p6-f55p, GHSA-c2c7-rcm5-vvqj |
| `nanoid` | 3.3.16 → **3.3.18** (via `vitest` → `vite` → `postcss`;
dev) | GHSA-2v37-7h3g-55p8 |

`npm audit` now reports **0 vulnerabilities**.

### Lint/format wiring

Adds `format`/`format:check` (prettier) + `lint`/`lint:fix` (eslint,
JS+JSON) wired to `.configs/`, so the post-merge lint-format autofix
(CLDMV/.github v4.21.0) has scripts to run when this merges into `next`.
eslint ignores the intentional-error scan fixture `tests/testfile.js`
and generated `src/data`; one dead unused var was removed so `lint` is
green. Repo-wide formatting drift is intentionally left for the autofix
to apply and commit back on the post-merge push.

## Validation

- `npm ci` clean against the regenerated lockfile (npm-10 compatible).
- Full suite green locally: **17 test files / 24 tests**, incl.
espree-11 AST parsing paths.
- `npm run lint` green; PR CI green (Node 22 + lts/*, CodeQL); the Lint
& Format job correctly skips on the feature PR.

## Supersedes / folds in

- **Closes on merge:** #15, #16, #17, #18 (the four dependency bumps).
- **#9** (security transitives targeting `hotfixes`): folded here.
`next` already carries newer `brace-expansion` (5.0.9) / `minimatch`
(10.2.6) than #9's targets and has no `js-yaml` in-tree, so #9 is moot
against `next` — its intent ships via this release instead of the
hotfixes lane.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: dependencies Relates to dependency updates, version bumps, or package management

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant