deps: bump @eslint/json from 0.13.0 to 2.0.1 - #17
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [@eslint/json](https://github.com/eslint/json) from 0.13.0 to 2.0.1. - [Release notes](https://github.com/eslint/json/releases) - [Changelog](https://github.com/eslint/json/blob/main/CHANGELOG.md) - [Commits](eslint/json@json-v0.13.0...json-v2.0.1) --- updated-dependencies: - dependency-name: "@eslint/json" dependency-version: 2.0.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
cldmv-bot
Bot
added
the
type: dependencies
This was referenced Aug 9, 2026
This was referenced Aug 9, 2026
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 If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/next/eslint/json-2.0.1
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.
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
1 participant
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 @eslint/json from 0.13.0 to 2.0.1.
Release notes
Sourced from @eslint/json's releases.
... (truncated)
Changelog
Sourced from @eslint/json's changelog.
... (truncated)
Commits
9ebeea3chore: release 2.0.1 🚀 (#245)ce22b12docs: Update README sponsors2ef892adocs: Update README sponsorse5d4f26docs: Update README sponsors82de68dchore: update non-major dev-dependencies to v3.8.4 (#247)99948f6docs: Update README sponsorscf262a6docs: Update README sponsors2202c87docs: Update README sponsors74731efchore: update@arethetypeswrong/clito 0.18.3 (#246)f262565fix: update dependency@eslint/plugin-kitto ^0.7.2 (#244)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@eslint/jsonsince your current version.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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)