Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update all non-major dependencies #25

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 15, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@iconify-json/simple-icons ^1.2.11 -> ^1.2.14 age adoption passing confidence devDependencies patch
@iconify-json/vscode-icons ^1.2.2 -> ^1.2.3 age adoption passing confidence devDependencies patch
@nuxt/eslint (source) ^0.6.0 -> ^0.7.2 age adoption passing confidence devDependencies minor
@nuxt/eslint (source) ^0.6.1 -> ^0.7.2 age adoption passing confidence dependencies minor
@nuxt/rspack-builder (source) ^3.12.2 -> ^3.14.1592 age adoption passing confidence devDependencies minor
@nuxt/ui-pro ^1.4.4 -> ^1.5.0 age adoption passing confidence dependencies minor
@vueuse/nuxt (source) ^11.2.0 -> ^11.3.0 age adoption passing confidence dependencies minor
axios (source) ^1.7.7 -> ^1.7.8 age adoption passing confidence dependencies patch
eslint (source) ^9.14.0 -> ^9.16.0 age adoption passing confidence devDependencies minor
lucide-vue-next (source) ^0.454.0 -> ^0.464.0 age adoption passing confidence dependencies minor
node 22.4.1-slim -> 22.11.0-slim age adoption passing confidence final minor
nuxt-og-image (source) 3.0.6 -> 3.1.1 age adoption passing confidence dependencies minor
nuxt-security (source) 2.0.0 -> 2.1.5 age adoption passing confidence dependencies minor
shiki (source) ^1.22.2 -> ^1.24.0 age adoption passing confidence dependencies minor
vitest (source) ^2.1.4 -> ^2.1.8 age adoption passing confidence devDependencies patch

Release Notes

nuxt/eslint (@​nuxt/eslint)

v0.7.2

Compare Source

   🚀 Features
    View changes on GitHub

v0.7.1

Compare Source

No significant changes

    View changes on GitHub

v0.7.0

Compare Source

   🚀 Features
    View changes on GitHub

v0.6.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.6.1

Compare Source

   🚀 Features
    View changes on GitHub
nuxt/nuxt (@​nuxt/rspack-builder)

v3.14.1592

Compare Source

3.14.1592 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes
  • rspack: Update webpackbar with support for rspack (#​29823)
  • nuxt: Assign default name to component without setup (#​29869)
  • kit: Use dst to deduplicate templates when adding them (#​29895)
  • nuxt: Handle empty plugin files (d44408e87)
  • vite: Use resolved nuxt template dst to invalidate modules (6cd3352de)
  • nuxt: Return null map for empty plugin metadata (302a66da9)
  • kit: Resolve module paths before appending subpaths (#​29955)
  • nuxt: Recompile templates on change events (#​29954)
  • nuxt: Do not include <NuxtWelcome> when building (#​29956)
  • nuxt: Allow scanning metadata from 2+ files at same path (#​29969)
  • nuxt: Do not disallow importing nitro dependencies (#​29975)
💅 Refactors
  • nuxt: Define layouts as async vue components (#​29957)
📖 Documentation
🏡 Chore
  • Remove unused imports and update eslint config (#​29876)
✅ Tests
🤖 CI
❤️ Contributors

v3.14.159

Compare Source

3.14.159 is a hotfix release to address regressions in v3.14.

We're leaning into the π theme - future patch releases of this minor version will just continue adding digits. (Sorry for any inconvenience! 😆)

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Update nitropack preset directory (#​29780)
  • kit: Fall back to meta version if there's no module.json (#​29793)
  • kit: Use mlly to resolve module paths to avoid cjs fallback (#​29799)
  • webpack,rspack: Add adapter for webpack-dev-middleware (#​29806)
  • nuxt: Remove null-byte prefix for virtual files (#​29809)
  • kit: Convert module path to file url before reading meta (fb833ac64)
📖 Documentation
🏡 Chore
❤️ Contributors
nuxt/ui-pro (@​nuxt/ui-pro)

v1.5.0

Compare Source

vueuse/vueuse (@​vueuse/nuxt)

v11.3.0

Compare Source

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

v1.7.8

Compare Source

Bug Fixes
Contributors to this release
eslint/eslint (eslint)

v9.16.0

Compare Source

Features

  • 8f70eb1 feat: Add ignoreComputedKeys option in sort-keys rule (#​19162) (Milos Djermanovic)

Documentation

  • 9eefc8f docs: fix typos in use-isnan (#​19190) (루밀LuMir)
  • 0c8cea8 docs: switch the order of words in no-unreachable (#​19189) (루밀LuMir)
  • 0c19417 docs: add missing backtick to no-async-promise-executor (#​19188) (루밀LuMir)
  • 8df9276 docs: add backtick in -0 in description of no-compare-neg-zero (#​19186) (루밀LuMir)
  • 7e16e3f docs: fix caseSensitive option's title of sort-keys (#​19183) (Tanuj Kanti)
  • 0c6b842 docs: fix typos in migration-guide.md (#​19180) (루밀LuMir)
  • 353266e docs: fix a typo in debug.md (#​19179) (루밀LuMir)
  • 5ff318a docs: delete unnecessary horizontal rule(---) in nodejs-api (#​19175) (루밀LuMir)
  • 576bcc5 docs: mark more rules as handled by TypeScript (#​19164) (Tanuj Kanti)
  • 742d054 docs: note that no-restricted-syntax can be used with any language (#​19148) (Milos Djermanovic)

Chores

v9.15.0

Compare Source

lucide-icons/lucide (lucide-vue-next)

v0.464.0: New icons 0.464.0

Compare Source

Modified Icons 🔨

v0.463.0: New icons 0.463.0

Compare Source

Modified Icons 🔨

v0.462.0: New icons 0.462.0

Compare Source

New icons 🎨

Modified Icons 🔨

v0.461.0: New icons 0.461.0

Compare Source

New icons 🎨

Modified Icons 🔨

v0.460.0: New icons 0.460.0

Compare Source

New icons 🎨

v0.459.0: New icons 0.459.0

Compare Source

New icons 🎨

v0.458.0: New icons 0.458.0

Compare Source

New icons 🎨

Modified Icons 🔨

Other Changes

Full Changelog: lucide-icons/lucide@0.457.0...0.458.0

v0.457.0: New icons 0.457.0

Compare Source

New icons 🎨

Modified Icons 🔨

v0.456.0: Choosing import name style 0.456.0

Compare Source

What's Changed

Adjustable icon naming imports

Customize import name styles for lucide-react, lucide-vue, lucide-react-native, lucide-preact, to manage autocompletion in your IDE.

  1. Turn off autocomplete in your IDE:
    Add the following to your settings.json
{
  "typescript.preferences.autoImportFileExcludePatterns": [
    "lucide-react",
    "lucide-preact",
    "lucide-react-native",
    "lucide-vue-next"
  ]
}
  1. Create a custom module declaration file:

It allows you to choose the import name style.

For React:

declare module "lucide-react" {
  // Prefixed import names
  export * from "lucide-react/dist/lucide-react.prefixed";
  // or
  // Suffixed import names
  export * from "lucide-react/dist/lucide-react.suffixed";
}

For Vue:

declare module "lucide-vue-next" {
  // Prefixed import names
  export * from "lucide-vue-next/dist/lucide-vue-next.prefixed";
  // or
  // Suffixed import names
  export * from "lucide-vue-next/dist/lucide-vue-next.suffixed";
}

v0.455.0: New icons 0.455.0

Compare Source

New icons 🎨

Modified Icons 🔨

nodejs/node (node)

v22.11.0: 2024-10-29, Version 22.11.0 'Jod' (LTS), @​richardlau

Compare Source

Notable Changes

This release marks the transition of Node.js 22.x into Long Term Support (LTS)
with the codename 'Jod'. The 22.x release line now moves into "Active LTS"
and will remain so until October 2025. After that time, it will move into
"Maintenance" until end of life in April 2027.

Other than updating metadata, such as the process.release object, to reflect
that the release is LTS, no further changes from Node.js 22.10.0 are included.

OpenSSL 3.x

Official binaries for Node.js 22.x currently include OpenSSL 3.0.x (more
specifically, the quictls OpenSSL fork).
OpenSSL 3.0.x is the currently designated long term support version that is
scheduled to be supported until 7th September 2026, which is within the expected
lifetime of Node.js 22.x. We are expecting upstream OpenSSL to announce a
successor long term support version prior to that date and since OpenSSL now
follows a semantic versioning-like versioning scheme we expect to be able to
update to the next long term supported version of OpenSSL during the lifetime of
Node.js 22.x.

v22.10.0: 2024-10-16, Version 22.10.0 (Current), @​aduh95

Compare Source

Notable Changes
New "module-sync" exports condition

This release introduces a "module-sync" exports condition that's enabled when
require(esm) is enabled, so packages can supply a synchronous ES module to the
Node.js module loader, no matter if it's being required or imported. This is
similar to the "module" condition that bundlers have been using to support
require(esm) in Node.js, and allows dual-package authors to opt into ESM-first
only on newer versions of Node.js that supports require(esm) to avoid the
dual-package hazard.

{
  "type": "module",
  "exports": {
    "node": {
      // On new version of Node.js, both require() and import get
      // the ESM version
      "module-sync": "./index.js",
      // On older version of Node.js, where "module-sync" and require(esm) are
      // not supported, use the CJS version to avoid dual-package hazard.
      // When package authors think it's time to drop support for older versions of
      // Node.js, they can remove the exports conditions and just use "main": "index.js".
      "default": "./dist/index.cjs"
    },
    // On any other environment, use the ESM version.
    "default": "./index.js"
  }
}

Or if the package is only meant to be run on Node.js and wants to fallback to
CJS on older versions that don't have require(esm):

{
  "type": "module",
  "exports": {
    // On new version of Node.js, both require() and import get the ESM version
    "module-sync": "./index.js",
    // On older version of Node.js, where "module-sync" and require(esm) are
    // not supported, use the CJS version to avoid dual-package hazard.
    // When package authors think it's time to drop support for older versions of
    // Node.js, they can remove the exports conditions and just use "main": "index.js".
    "default": "./dist/index.cjs"
  }
}

For package authors: this only serves as a feature-detection mechanism for
packages that wish to support both CJS and ESM users during the period when some
active Node.js LTS versions support require(esm) while some older ones don't.
When all active Node.js LTS lines support require(esm), packages can simplify
their distributions by bumping the major version, dropping their CJS exports,
and removing the module-sync exports condition (with only main or default
targetting the ESM exports). If the package needs to support both bundlers and
being run unbundled on Node.js during the transition period, use both
module-sync and module and point them to the same ESM file. If the package
already doesn't want to support older versions of Node.js that doesn't support
require(esm), don't use this export condition.

For bundlers/tools: they should avoid implementing this stop-gap condition.
Most existing bundlers implement the de-facto bundler standard
module
exports condition, and that should be enough to support users who want to bundle
ESM from CJS consumers. Users who want both bundlers and Node.js to recognize
the ESM exports can use both module/module-sync conditions during the
transition period, and can drop module-sync+module when they no longer need
to support older versions of Node.js. If tools do want to support this
condition, it's recommended to make the resolution rules in the graph pointed by
this condition match the Node.js native ESM rules to avoid divergence.

We ended up implementing a condition with a different name instead of reusing
"module", because existing code in the ecosystem using the "module"
condition sometimes also expect the module resolution for these ESM files to
work in CJS style, which is supported by bundlers, but the native Node.js loader
has intentionally made ESM resolution different from CJS resolution (e.g.
forbidding import './noext' or import './directory'), so it would be
breaking to implement a "module" condition without implementing the forbidden
ESM resolution rules. For now, this just implements a new condition as
semver-minor so it can be backported to older LTS.

Contributed by Joyee Cheung in #​54648.

node --run is now stable

This CLI flag runs a specified command from a package.json's "scripts" object.

For the following package.json:

{
  "scripts": {
    "test": "node --test-reporter junit --test ./test"
  }
}

You can run node --run test and that would start the test suite.

Contributed by Yagiz Nizipli in #​53763.

Other notable changes
  • [f0b441230a] - (SEMVER-MINOR) crypto: add KeyObject.prototype.toCryptoKey (Filip Skokan) #​55262
  • [349d2ed07b] - (SEMVER-MINOR) crypto: add Date fields for validTo and validFrom (Andrew Moon) #​54159
  • [bebc95ed58] - doc: add abmusse to collaborators (Abdirahim Musse) #​55086
  • [914db60159] - (SEMVER-MINOR) http2: expose nghttp2_option_set_stream_reset_rate_limit as an option (Maël Nison) #​54875
  • [f7c3b03759] - (SEMVER-MINOR) lib: propagate aborted state to dependent signals before firing events (jazelly) #​54826
  • [32261fc98a] - (SEMVER-MINOR) module: support loading entrypoint as url (RedYetiDev) #​54933
  • [06957ff355] - (SEMVER-MINOR) module: implement flushCompileCache() (Joyee Cheung) #​54971
  • [2dcf70c347] - (SEMVER-MINOR) module: throw when invalid argument is passed to enableCompileCache() (Joyee Cheung) #​54971
  • [f9b19d7c44] - (SEMVER-MINOR) module: write compile cache to temporary file and then rename it (Joyee Cheung) #​54971
  • [e95163b170] - (SEMVER-MINOR) process: add process.features.require_module (Joyee Cheung) #​55241
  • [4050f68e5d] - (SEMVER-MINOR) process: add process.features.typescript (Aviv Keller) #​54295
  • [86f7cb802d] - (SEMVER-MINOR) test_runner: support custom arguments in run() (Aviv Keller) #​55126
  • [b62f2f8259] - (SEMVER-MINOR) test_runner: add 'test:summary' event (Colin Ihrig) #​54851
  • [d7c708aec5] - (SEMVER-MINOR) test_runner: add support for coverage via run() (Chemi Atlow) #​53937
  • [5fda4a1498] - (SEMVER-MINOR) worker: add markAsUncloneable api (Jason Zhang) #​55234
Commits

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 15b65c2 to 6bf787b Compare October 20, 2024 18:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from 7aab87e to ab9a99b Compare October 30, 2024 20:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 02a1826 to 655139b Compare November 8, 2024 17:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from be22628 to 197f9b4 Compare November 19, 2024 15:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from a8e7b1a to 9b57ccb Compare November 26, 2024 06:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from c3ec1bf to a5d8c5d Compare December 3, 2024 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants