Skip to content

chore(deps): update all non-major dependencies#160

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/all-minor-patch
Open

chore(deps): update all non-major dependencies#160
renovate[bot] wants to merge 1 commit intomainfrom
renovate/all-minor-patch

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 2, 2026

This PR contains the following updates:

Package Change Age Confidence
@eslint-community/eslint-plugin-eslint-comments ^4.6.0^4.7.1 age confidence
@eslint/config-inspector ^1.4.2^1.5.0 age confidence
@types/node (source) ^25.3.2^25.3.5 age confidence
@typescript/native-preview (source) 7.0.0-dev.20260227.17.0.0-dev.20260306.1 age confidence
@unocss/eslint-plugin (source) ^66.6.2^66.6.6 age confidence
eslint (source) ^10.0.2^10.0.3 age confidence
eslint-plugin-baseline-js (source) ^0.5.0^0.6.1 age confidence
eslint-plugin-de-morgan ^2.0.0^2.1.1 age confidence
eslint-plugin-yml (source) ^3.3.0^3.3.1 age confidence
globals ^17.3.0^17.4.0 age confidence
tsdown (source) ^0.21.0-beta.2^0.21.0 age confidence
unrun (source) ^0.2.28^0.2.30 age confidence

Release Notes

eslint-community/eslint-plugin-eslint-comments (@​eslint-community/eslint-plugin-eslint-comments)

v4.7.1

Compare Source

Bug Fixes
  • no-unused-disable: update deprecated info structure (#​310) (de04980)

v4.7.0

Compare Source

Features
eslint/config-inspector (@​eslint/config-inspector)

v1.5.0

Compare Source

Features
  • update deps, support eslint v10 (8e00b7e)
microsoft/typescript-go (@​typescript/native-preview)

v7.0.0-dev.20260306.1

Compare Source

v7.0.0-dev.20260305.1

Compare Source

v7.0.0-dev.20260304.1

Compare Source

v7.0.0-dev.20260303.1

Compare Source

v7.0.0-dev.20260302.1

Compare Source

v7.0.0-dev.20260301.1

Compare Source

v7.0.0-dev.20260228.1

Compare Source

unocss/unocss (@​unocss/eslint-plugin)

v66.6.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v66.6.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v66.6.4

Compare Source

   🚀 Features
    View changes on GitHub

v66.6.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
eslint/eslint (eslint)

v10.0.3

Compare Source

3ru/eslint-plugin-baseline-js (eslint-plugin-baseline-js)

v0.6.1

Compare Source

Bug Fixes

v0.6.0

Compare Source

Bug Fixes
  • eliminate shadowed-global false positives and enforce descriptor consistency (#​103) (d3cec0f)
Features
azat-io/eslint-plugin-de-morgan (eslint-plugin-de-morgan)

v2.1.1

Compare Source

compare changes

🐞 Bug Fixes
  • Add explicit type annotation to configs export
    (2dab08c)
❤️ Contributors

v2.1.0

Compare Source

compare changes

🚀 Features
❤️ Contributors
ota-meshi/eslint-plugin-yml (eslint-plugin-yml)

v3.3.1

Compare Source

Patch Changes
sindresorhus/globals (globals)

v17.4.0

Compare Source

rolldown/tsdown (tsdown)

v0.21.0

Compare Source

v0.21.0 - Notable Changes

Breaking Changes
Dependency options renamed to deps namespace

The dependency-related options have been moved under a new deps namespace with clearer names:

  • external -> deps.neverBundle
  • noExternal -> deps.alwaysBundle
  • inlineOnly -> deps.onlyAllowBundle
  • skipNodeModulesBundle -> deps.skipNodeModulesBundle

Before:

export default defineConfig({
  external: ['vue'],
  noExternal: ['lodash'],
})

After:

export default defineConfig({
  deps: {
    neverBundle: ['vue'],
    alwaysBundle: ['lodash'],
  },
})

The old options still work but are deprecated and will emit warnings.

failOnWarn default changed from 'ci-only' to false

If you relied on the previous behavior where warnings would fail the build in CI environments, you now need to explicitly set failOnWarn: true or failOnWarn: 'ci-only' in your config.

Node.js < 22.18.0 deprecated

tsdown now emits a deprecation warning when running on Node.js versions below 22.18.0. Plan to upgrade your Node.js version accordingly.

New Features
Experimental Node.js SEA executable bundling (exe)

tsdown can now bundle your TypeScript project into a standalone executable using Node.js Single Executable Applications (SEA). A new @tsdown/exe package provides cross-platform executable building support. See the exe documentation for details.

export default defineConfig({
  exe: true, // or { useCodeCache: true, useSnapshot: true }
})
Full CSS pipeline with @tsdown/css

CSS handling has been reimplemented as a native Rolldown plugin and extracted into the @tsdown/css package, providing a complete CSS pipeline with Lightning CSS and PostCSS support via the css.transformer option. See the CSS documentation for details.

inlinedDependencies field in package.json

When using the exports feature, tsdown now auto-generates an inlinedDependencies field in your package.json, listing dependencies that are bundled into the output.

Object option for customExports

customExports now supports an object format for more fine-grained control over the generated exports field.

Migration Guide
  1. Update dependency options: Rename external -> deps.neverBundle, noExternal -> deps.alwaysBundle, etc.
  2. Check failOnWarn: If you need warnings to fail the build in CI, explicitly set failOnWarn: 'ci-only' or failOnWarn: true.
  3. Upgrade Node.js: Ensure you're running Node.js >= 22.18.0 to avoid deprecation warnings.
Links

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.0-beta.5

Compare Source

v0.21.0-beta.5 - Notable Changes

Breaking Changes
Dependency options renamed to deps namespace

The dependency-related options have been moved under a new deps namespace with clearer names:

  • external -> deps.neverBundle
  • noExternal -> deps.alwaysBundle
  • inlineOnly -> deps.onlyAllowBundle
  • skipNodeModulesBundle -> deps.skipNodeModulesBundle

Before:

export default defineConfig({
  external: ['vue'],
  noExternal: ['lodash'],
})

After:

export default defineConfig({
  deps: {
    neverBundle: ['vue'],
    alwaysBundle: ['lodash'],
  },
})

The old options still work but are deprecated and will emit warnings.

failOnWarn default changed from 'ci-only' to false

If you relied on the previous behavior where warnings would fail the build in CI environments, you now need to explicitly set failOnWarn: true or failOnWarn: 'ci-only' in your config.

Node.js < 22.18.0 deprecated

tsdown now emits a deprecation warning when running on Node.js versions below 22.18.0. Plan to upgrade your Node.js version accordingly.

New Features
Experimental Node.js SEA executable bundling (exe)

tsdown can now bundle your TypeScript project into a standalone executable using Node.js Single Executable Applications (SEA). A new @tsdown/exe package provides cross-platform executable building support. See the exe documentation for details.

export default defineConfig({
  exe: true, // or { useCodeCache: true, useSnapshot: true }
})
Full CSS pipeline with @tsdown/css

CSS handling has been reimplemented as a native Rolldown plugin and extracted into the @tsdown/css package, providing a complete CSS pipeline with Lightning CSS and PostCSS support via the css.transformer option. See the CSS documentation for details.

inlinedDependencies field in package.json

When using the exports feature, tsdown now auto-generates an inlinedDependencies field in your package.json, listing dependencies that are bundled into the output.

Object option for customExports

customExports now supports an object format for more fine-grained control over the generated exports field.

Migration Guide
  1. Update dependency options: Rename external -> deps.neverBundle, noExternal -> deps.alwaysBundle, etc.
  2. Check failOnWarn: If you need warnings to fail the build in CI, explicitly set failOnWarn: 'ci-only' or failOnWarn: true.
  3. Upgrade Node.js: Ensure you're running Node.js >= 22.18.0 to avoid deprecation warnings.
Links

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.0-beta.4

Compare Source

   🚀 Features
    View changes on GitHub

v0.21.0-beta.3

Compare Source

v0.21.0-beta.3 - Notable Changes

Breaking Changes
Dependency options renamed to deps namespace

The dependency-related options have been moved under a new deps namespace with clearer names:

  • external -> deps.neverBundle
  • noExternal -> deps.alwaysBundle
  • inlineOnly -> deps.onlyAllowBundle
  • skipNodeModulesBundle -> deps.skipNodeModulesBundle

Before:

export default defineConfig({
  external: ['vue'],
  noExternal: ['lodash'],
})

After:

export default defineConfig({
  deps: {
    neverBundle: ['vue'],
    alwaysBundle: ['lodash'],
  },
})

The old options still work but are deprecated and will emit warnings.

failOnWarn default changed from 'ci-only' to false

If you relied on the previous behavior where warnings would fail the build in CI environments, you now need to explicitly set failOnWarn: true or failOnWarn: 'ci-only' in your config.

Node.js < 22.18.0 deprecated

tsdown now emits a deprecation warning when running on Node.js versions below 22.18.0. Plan to upgrade your Node.js version accordingly.

New Features
Experimental Node.js SEA executable bundling (exe)

tsdown can now bundle your TypeScript project into a standalone executable using Node.js Single Executable Applications (SEA). A new @tsdown/exe package provides cross-platform executable building support. See the exe documentation for details.

export default defineConfig({
  exe: true, // or { useCodeCache: true, useSnapshot: true }
})
Full CSS pipeline as Rolldown plugin

CSS handling has been reimplemented as a native Rolldown plugin, providing a complete CSS pipeline with Lightning CSS integration for transforms, minification, and bundling. See the CSS documentation for details.

inlinedDependencies field in package.json

When using the exports feature, tsdown now auto-generates an inlinedDependencies field in your package.json, listing dependencies that are bundled into the output.

Object option for customExports

customExports now supports an object format for more fine-grained control over the generated exports field.

Migration Guide
  1. Update dependency options: Rename external -> deps.neverBundle, noExternal -> deps.alwaysBundle, etc.
  2. Check failOnWarn: If you need warnings to fail the build in CI, explicitly set failOnWarn: 'ci-only' or failOnWarn: true.
  3. Upgrade Node.js: Ensure you're running Node.js >= 22.18.0 to avoid deprecation warnings.
Links

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
Gugustinette/unrun (unrun)

v0.2.30

Compare Source

   🚀 Features
    View changes on GitHub

v0.2.29

Compare Source

   🚀 Features
    View changes on GitHub

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

@vercel
Copy link

vercel bot commented Mar 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
eslint-config Ready Ready Preview, Comment Mar 7, 2026 1:06am

@renovate renovate bot added the dependencies label Mar 2, 2026
@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Mar 2, 2026

Open in StackBlitz

npm i https://pkg.pr.new/@sxzz/eslint-config@160

commit: 3264759

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5cdd47d to bbfa4dc Compare March 2, 2026 09:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from bbfa4dc to 4858428 Compare March 2, 2026 14:17
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4858428 to 740f09f Compare March 3, 2026 10:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 740f09f to 312d8e4 Compare March 3, 2026 13:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 312d8e4 to f350bd0 Compare March 3, 2026 18:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f350bd0 to 5a0758d Compare March 4, 2026 02:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5a0758d to 8ab3e7f Compare March 4, 2026 09:18
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8ab3e7f to f244427 Compare March 4, 2026 12:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f244427 to aa9524a Compare March 5, 2026 04:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from aa9524a to 283c546 Compare March 5, 2026 10:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 283c546 to f1799cc Compare March 6, 2026 02:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f1799cc to 474b972 Compare March 6, 2026 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants