Skip to content

deps: bump espree from 9.6.1 to 11.2.0 - #15

Closed
dependabot[bot] wants to merge 1 commit into
nextfrom
dependabot/npm_and_yarn/next/espree-11.2.0
Closed

deps: bump espree from 9.6.1 to 11.2.0#15
dependabot[bot] wants to merge 1 commit into
nextfrom
dependabot/npm_and_yarn/next/espree-11.2.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 5, 2026

Copy link
Copy Markdown

Bumps espree from 9.6.1 to 11.2.0.

Release notes

Sourced from espree's releases.

espree: v11.2.0

11.2.0 (2026-03-04)

Features

  • allow top level using declaration in "commonjs" (#734) (3f7fb58)

espree: v11.1.1

11.1.1 (2026-02-20)

Bug Fixes

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • eslint-visitor-keys bumped from ^5.0.0 to ^5.0.1

espree: v11.1.0

11.1.0 (2026-01-18)

Features

Bug Fixes

  • restore comments property on tokenize() return value (#721) (5603ea9)

espree: v11.0.0

11.0.0 (2025-11-07)

⚠ BREAKING CHANGES

  • Program range span entire source text (#677)
  • Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#696)

Features

  • Program range span entire source text (#677) (68bbb74)

... (truncated)

Changelog

Sourced from espree's changelog.

11.2.0 (2026-03-04)

Features

  • allow top level using declaration in "commonjs" (#734) (3f7fb58)

11.1.1 (2026-02-20)

Bug Fixes

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • eslint-visitor-keys bumped from ^5.0.0 to ^5.0.1

11.1.0 (2026-01-18)

Features

Bug Fixes

  • restore comments property on tokenize() return value (#721) (5603ea9)

11.0.0 (2025-11-07)

⚠ BREAKING CHANGES

  • Program range span entire source text (#677)
  • Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#696)

Features

  • Program range span entire source text (#677) (68bbb74)
  • Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#696) (9c84ecb)

Dependencies

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for espree since your current version.


@cldmv-bot cldmv-bot Bot added the type: dependencies Relates to dependency updates, version bumps, or package management label Aug 5, 2026
Bumps [espree](https://github.com/eslint/js/tree/HEAD/packages/espree) from 9.6.1 to 11.2.0.
- [Release notes](https://github.com/eslint/js/releases)
- [Changelog](https://github.com/eslint/js/blob/main/packages/espree/CHANGELOG.md)
- [Commits](https://github.com/eslint/js/commits/espree-v11.2.0/packages/espree)

---
updated-dependencies:
- dependency-name: espree
  dependency-version: 11.2.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/next/espree-11.2.0 branch from 3f9c24c to dde1b78 Compare August 5, 2026 10:58
@Shinrai

Shinrai commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Superseded by #20, which consolidates this bump (espree → 11.2.0) with #16/#17/#18 into a single PR onto next, verified green (npm ci clean, 24/24 tests, full CI matrix). Closing.

@dependabot @github

dependabot Bot commented on behalf of github Aug 9, 2026

Copy link
Copy Markdown
Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/next/espree-11.2.0 branch August 9, 2026 19:48
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