chore(deps): update all non-major dependencies

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@nuxt/eslint-config (source)	^1.12.1 → ^1.16.0
@types/node (source)	^25.0.2 → ^25.9.4
c12	^3.3.2 → ^3.3.4
citty	^0.1.6 → ^0.2.2
eslint (source)	^9.39.2 → ^9.39.4
glob	^13.0.0 → ^13.0.6
markdownlint	^0.40.0 → ^0.41.0
pnpm (source)	10.26.0 → 10.34.4
release-it	^19.1.0 → ^19.2.4

---

Release Notes

nuxt/eslint (@​nuxt/eslint-config)

v1.16.0

Compare Source

   🚀 Features

• Update deps  -  by @​antfu (008ad)

    View changes on GitHub

v1.15.2

Compare Source

   🐞 Bug Fixes

• Prevent race condition of running checker module before eslint config is written  -  by @​sebbayer in #​653 (69aa4)

    View changes on GitHub

v1.15.1

Compare Source

   🐞 Bug Fixes

• Downgrade @eslint/js, fix #​647  -  by @​antfu in #​647 (2c1c1)

    View changes on GitHub

v1.15.0

Compare Source

   🚀 Features

• Relax peer deps range to support ESLint v10, fix #​642  -  by @​antfu in #​642 (305a9)

    View changes on GitHub

v1.14.0

Compare Source

   🚀 Features

• eslint-config: Add no-page-meta-runtime-values  -  by @​danielroe in #​641 (b74a0)

    View changes on GitHub

v1.13.0

Compare Source

   🚀 Features

• Upgrade eslint-flat-config-utils eslint-plugin-import-lite and eslint-plugin-jsdoc  -  by @​antfu (10bf9)

    View changes on GitHub

unjs/c12 (c12)

v3.3.4

Compare Source

compare changes

🏡 Chore

• Update deps (fe676ce)
• Bump giget to v3 (3cecdd3)

📦 Build

• Simplify exports field (99cb66f)

v3.3.3

Compare Source

compare changes

📦 Build

• Update chokidar to 5.x (0dcf338)

🏡 Chore

• Update dev deps (78ca00b)

❤️ Contributors

• Pooya Parsa (@​pi0)

unjs/citty (citty)

v0.2.2

Compare Source

compare changes

🚀 Enhancements

• Support subcommand aliases (#​236)
• Add plugin system (#​238)
• default: Support default sub command (#​156)

🩹 Fixes

• main: Allow user-defined -h, --help, -v, --version args (#​234)
• Resolve alias value over default (#​228)
• Subcommand resolution incorrectly consumes flag values (#​231)
• Coerce parsed arg values to match declared types (#​239)

💅 Refactors

• Improve usage tips (#​198)

📖 Documentation

• Add usage section (#​70)
• Add example setup and cleanup option (#​188)

🏡 Chore

• Update deps (49b416e)
• Init agents.md (3bee5c3)
• Apply automated updates (142bdc9)
• Rename fmt script (64e8f54)
• Apply automated updates (0228318)
• Apply automated updates (f509073)
• Update deps (033daea)

✅ Tests

• Reproduce issue with short option (alias) and = (#​230)
• parser: Add regression tests for hyphen-prefixed string values (#​171)

❤️ Contributors

• 苏向夜 (@​fu050409)
• Pooya Parsa (@​pi0)
• Daniel Roe (@​danielroe)
• Kricsleo (@​kricsleo)
• Kanon (@​ysknsid25)
• Estéban (@​Barbapapazes)
• Robin robin.kehl@singular-it.de
• Wyatt Johnson accounts+github@wyattjoh.ca

v0.2.1

Compare Source

compare changes

🩹 Fixes

• Propagate --no- negation to aliases and main option (#​225)

🏡 Chore

• Fix readme formatting (#​223)
• Use oxlint and oxfmt (f1d05f4)

❤️ Contributors

• Pooya Parsa (@​pi0)
• Kai Gritun kaigritun@gmail.com
• Jimmy Guzman (@​jimmy-guzman)

v0.2.0

Compare Source

compare changes

🚀 Enhancements

• Support hidden meta to hide command (#​111)
• Support enum arg type (#​83)
• Support number arg type (#​73)
• Support negativeDescription for args (#​40)
• ⚠️ Parsed optionals and enum type safety (#​174)

🩹 Fixes

• ⚠️ Conditionally print negative boolean argument usage (#​177)
• types: Value type of NumberArgDef should be number (#​183)
• Show cli error message (#​186)
• Allow number arg to be optional (#​194)

💅 Refactors

• Show error once (#​167)
• More strict types (f597897)
• ⚠️ Use node:util.parseArgs for arg parsing (#​218)
• Use simple console formatting (#​219)

📦 Build

• ⚠️ Esm-only dist (42b57b0)

🏡 Chore

• Use automd for badges (b8371c4)
• Apply automated lint fixes (34c52a2)
• Fix typos (#​143)
• Update repo (d1ed3b4)
• Fix ci script (e13cb1e)
• Apply automated updates (3838771)
• Add vitest.config (eb5c799)
• Update dependencies (5d0a84e)
• Remove extra file (b90a84a)

✅ Tests

• Add unit tests for internal utils (#​77)
• Add test for args (#​160)
• Add test for runMain (#​162)
• Add test for usage (#​161)
• Add test for parser (#​192)
• Add test for subcommand (#​191)

⚠️ Breaking Changes

• ⚠️ Parsed optionals and enum type safety (#​174)
• ⚠️ Conditionally print negative boolean argument usage (#​177)
• ⚠️ Use node:util.parseArgs for arg parsing (#​218)
• ⚠️ Esm-only dist (42b57b0)

❤️ Contributors

• Pooya Parsa (@​pi0)
• Kricsleo (@​kricsleo)
• Kanon (@​ysknsid25)
• Bobbie Goede bobbiegoede@gmail.com
• Estéban (@​Barbapapazes)
• IWANABETHATGUY <974153916@​qq.com>
• Kentaro Suzuki mail@sushichan.live
• Xjccc (@​xjccc)
• Zuixinwang (@​zuixinwang)
• K-Sato <satokatsuki0130@​gmail.com>
• Lsh (@​peterroe)

eslint/eslint (eslint)

v9.39.4

Compare Source

Bug Fixes

• f18f6c8 fix: update dependency minimatch to ^3.1.5 (#​20564) (Milos Djermanovic)
• a3c868f fix: update dependency @​eslint/eslintrc to ^3.3.4 (#​20554) (Milos Djermanovic)
• 234d005 fix: minimatch security vulnerability patch for v9.x (#​20549) (Andrej Beles)
• b1b37ee fix: update ajv to 6.14.0 to address security vulnerabilities (#​20538) (루밀LuMir)

Documentation

• 4675152 docs: add deprecation notice partial (#​20520) (Milos Djermanovic)

Chores

• b8b4eb1 chore: update dependencies for ESLint v9.39.4 (#​20596) (Francesco Trotta)
• 71b2f6b chore: package.json update for @​eslint/js release (Jenkins)
• 1d16c2f ci: pin Node.js 25.6.1 (#​20563) (Milos Djermanovic)

v9.39.3

Compare Source

Bug Fixes

• 791bf8d fix: restore TypeScript 4.0 compatibility in types (#​20504) (sethamus)

Chores

• 8594a43 chore: upgrade @​eslint/js@​9.39.3 (#​20529) (Milos Djermanovic)
• 9ceef92 chore: package.json update for @​eslint/js release (Jenkins)
• af498c6 chore: ignore /docs/v9.x in link checker (#​20453) (Milos Djermanovic)

isaacs/node-glob (glob)

v13.0.6

Compare Source

v13.0.5

Compare Source

v13.0.4

Compare Source

v13.0.3

Compare Source

v13.0.2

Compare Source

v13.0.1

Compare Source

DavidAnson/markdownlint (markdownlint)

v0.41.0

Compare Source

• Improve MD022/MD028/MD035/MD042/MD051/MD060
• Remove handling of inline directive syntax (frequent false positives)
• Remove deprecated Options.resultVersion (breaking change)
• Remove deprecated LintResults.toString (breaking change)
• Remove support for end-of-life Node version 20
• Update dependencies

pnpm/pnpm (pnpm)

v10.34.4

Compare Source

v10.34.3

Compare Source

v10.34.2

Compare Source

v10.34.1: pnpm 10.34.1

Compare Source

Patch Changes

• Reject pnpm-lock.yaml entries whose remote tarball resolution: block is missing the integrity field. Previously the worker that extracts a downloaded tarball skipped hash verification when no integrity was supplied and minted a fresh one from the unverified bytes, so an attacker who could both alter the lockfile (e.g. via a pull request that strips integrity:) and serve modified content at the referenced tarball URL could install a tampered package without any error — including under --frozen-lockfile. pnpm now fails closed at lockfile-read time with ERR_PNPM_MISSING_TARBALL_INTEGRITY. Git-hosted tarballs (gitHosted: true or a URL on codeload.github.com / bitbucket.org / gitlab.com) and file: tarballs are exempt — the commit SHA in a git-host URL and the user-controlled local path already anchor the bytes.

Platinum Sponsors

Gold Sponsors

v10.34.0: pnpm 10.34

Compare Source

Minor Changes

• Treat tarball-integrity mismatches against the lockfile as a hard failure by default. Previously, pnpm install (non-frozen) would log ERR_PNPM_TARBALL_INTEGRITY, silently re-resolve from the registry, and overwrite the locked integrity — which meant a compromised registry, proxy, or republished version could substitute attacker-controlled content on a clean machine even though the project shipped a committed lockfile.

  pnpm install now exits with ERR_PNPM_TARBALL_INTEGRITY and a hint pointing at the new opt-in flag.

  The only opt-in is pnpm install --update-checksums — narrowly scoped to refreshing the locked integrity values from what the registry currently serves. Mirrors yarn's flag of the same name. A warning still prints when the bypass takes effect so the operation is auditable.

  --force and pnpm update deliberately do not bypass the integrity check. They are routine refresh operations; silently overwriting a locked integrity in those flows would erase the protection a committed lockfile is supposed to provide. --frozen-lockfile behavior is unchanged. --fix-lockfile keeps its documented purpose (filling in missing lockfile entries) and is also not a bypass.

Patch Changes

• Pin unscoped per-registry settings (_authToken, _auth, username/_password, tokenHelper, inline cert/key) to the registry declared in the same config source at load time, so a later layer overriding registry= (workspace .npmrc, pnpm-workspace.yaml, CLI --registry) cannot redirect a credential or client certificate authored for a different host. A deprecation warning is emitted whenever an unscoped per-registry setting is encountered, naming the source and the URL it was pinned to. Reported by JUNYI LIU.
• Fixed minimumReleaseAge handling when cached metadata is abbreviated. The npm registry returns abbreviated package metadata (without the per-version time field) by default, which made the maturity check throw ERR_PNPM_MISSING_TIME whenever cached abbreviated metadata was reused. pnpm now upgrades cached abbreviated metadata to the full document via a follow-up fetch when minimumReleaseAge is active, persists the upgrade to the on-disk cache so subsequent installs skip the extra fetch, and lets ERR_PNPM_MISSING_TIME from the cache fast-path fall through to the network fetch even under strict mode.
• Reject git resolutions whose commit field is not a 40-character hexadecimal SHA before invoking git. A malicious lockfile could otherwise smuggle a value such as --upload-pack=<command> through git fetch / git checkout, which on SSH or local-file transports executes the supplied command.
• Reject patch files whose diff --git headers reference paths outside the patched package directory. Previously a malicious .patch file added via a pull request could write, delete, or rename arbitrary files reachable by the user running pnpm install.
• Fixed --prefix=<dir> not being honored when locating the workspace root. The --prefix → dir rename was applied after workspace detection, so workspace settings declared in <dir>/pnpm-workspace.yaml were not loaded when pnpm was invoked from outside <dir> #​11535.
• Reject dependency aliases that contain path-traversal segments (such as @x/../../../../../.git/hooks) when reading them from a package manifest or symlinking them into node_modules. A malicious registry package could otherwise use a transitive dependency key to make pnpm install create symlinks at attacker-chosen paths outside the intended node_modules directory.

Platinum Sponsors

Gold Sponsors

v10.33.4: pnpm 10.33.4

Compare Source

Patch Changes

• Pin the integrity of git-hosted tarballs (codeload.github.com, gitlab.com, bitbucket.org) in the lockfile so that subsequent installs detect a tampered or substituted tarball and refuse to install it. Previously the lockfile only stored the tarball URL for git dependencies, so a compromised git host or a man-in-the-middle could serve arbitrary code on later installs without lockfile changes.

  A new gitHosted: true field is recorded on git-hosted tarball resolutions in the lockfile, letting every reader/writer route them by a single typed check instead of pattern-matching the tarball URL in each call site. Lockfiles written by older pnpm versions are enriched on load (URL fallback) so the field can be relied on uniformly across the codebase.

• Fix a regression where pnpm --recursive --filter '!<pkg>' run/exec/test/add would include the workspace root in the matched projects. The workspace root is now correctly excluded by default when only negative --filter arguments are provided, matching the documented behavior. To include the root, pass --include-workspace-root #​11341.

Platinum Sponsors

Gold Sponsors

v10.33.3

Compare Source

v10.33.2

Compare Source

v10.33.1: pnpm 10.33.1

Compare Source

Patch Changes

• When a project's packageManager field selects pnpm v11 or newer, commands that v10 would have passed through to npm (version, login, logout, publish, unpublish, deprecate, dist-tag, docs, ping, search, star, stars, unstar, whoami, etc.) are now handed over to the wanted pnpm, which implements them natively. Previously they silently shelled out to npm — making, for example, pnpm version --help print npm's help on a project with packageManager: pnpm@11.0.0-rc.3 #​11328.

Platinum Sponsors

Gold Sponsors

v10.33.0

Compare Source

v10.32.1: pnpm 10.32.1

Compare Source

Patch Changes

• Fix a regression where pnpm-workspace.yaml without a packages field caused all directories to be treated as workspace projects. This broke projects that use pnpm-workspace.yaml only for settings (e.g. minimumReleaseAge) without defining workspace packages #​10909.

Platinum Sponsors

Gold Sponsors

v10.32.0: pnpm 10.32

Compare Source

Minor Changes

• Added --all flag to pnpm approve-builds that approves all pending builds without interactive prompts #​10136.

Patch Changes

• Reverted change related to setting explicitly the npm config file path, which caused regressions.
• Reverted fix related to lockfile-include-tarball-url. Fixes #​10915.

Platinum Sponsors

Gold Sponsors

v10.31.0

Compare Source

v10.30.3

Compare Source

v10.30.2

Compare Source

v10.30.1: pnpm 10.30.1

Compare Source

Patch Changes

• Use the /-/npm/v1/security/audits/quick endpoint as the primary audit endpoint, falling back to /-/npm/v1/security/audits when it fails [#​10649](https://

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "on Monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[pkg-pr-new]

npm i https://pkg.pr.new/mdclint@15

commit: 1cc77fb

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

 ERR_PNPM_MISSING_TARBALL_INTEGRITY  Cannot install package "remark-mdc@https://pkg.pr.new/remark-mdc@305e886": its lockfile entry has no "integrity" field, so pnpm cannot verify the downloaded tarball.

The lockfile may be corrupted or have been tampered with. Restore it from a trusted source, or delete it and re-run installation without --frozen-lockfile to regenerate.