Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 28, 2025

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Change Age Confidence Type Update
@iconify-json/lucide ^1.2.56 -> ^1.2.68 age confidence dependencies patch
@nuxt/cli (source) ^3.25.1 -> ^3.28.0 age confidence devDependencies minor
@nuxt/eslint (source) ^1.5.2 -> ^1.9.0 age confidence devDependencies minor
@nuxt/eslint-config (source) ^1.5.2 -> ^1.9.0 age confidence devDependencies minor
@playwright/test (source) 1.53.2 -> 1.55.1 age confidence devDependencies minor
@types/node (source) ^22.16.0 -> ^22.18.6 age confidence devDependencies minor
danielroe/provenance-action v0.1.0 -> v0.1.1 age confidence action patch
eslint (source) ^9.30.1 -> ^9.36.0 age confidence devDependencies minor
mcr.microsoft.com/playwright v1.53.2-noble -> v1.55.1-noble age confidence container minor
pkg-types ^2.2.0 -> ^2.3.0 age confidence devDependencies minor
pnpm (source) 10.12.4 -> 10.17.1 age confidence packageManager minor
tailwindcss (source) 4.1.11 -> 4.1.13 age confidence dependencies patch
tinyglobby (source) ^0.2.14 -> ^0.2.15 age confidence devDependencies patch
turbo (source) 2.5.4 -> 2.5.7 age confidence devDependencies patch
typescript (source) 5.8.3 -> 5.9.2 age confidence devDependencies minor
vue (source) 3.5.17 -> 3.5.21 age confidence devDependencies patch
vue (source) 3.5.17 -> 3.5.21 age confidence resolutions patch
vue-tsc (source) 3.0.4 -> 3.0.8 age confidence devDependencies patch

Release Notes

nuxt/cli (@​nuxt/cli)

v3.28.0

Compare Source

3.28.0 is the next minor release.

👉 Changelog

compare changes

🚀 Enhancements
  • init: Add --nightly flag (#​650)
🩹 Fixes
  • dev: Handle array of dotenv file names (73888d3)
  • init: Use amended directory when adding modules (#​998)
  • init: Skip modules that are dependencies of the selected template (#​910)
  • init: Default nightly install to latest (6b80c59)
  • dev: End websocket connections gracefully (#​1001)
  • upgrade: Do not use cache when getting nuxt version (#​1002)
🏡 Chore
🤖 CI
  • Run size compare workflow on pull_request_target (#​999)
❤️ Contributors

v3.27.0

Compare Source

3.27.0 is the next minor release.

Timetable: to be announced.

👉 Changelog

compare changes

🚀 Enhancements
  • Add -e alias for --extends (#​986)
🩹 Fixes
  • upgrade: Update default Nuxt version to v4 (#​981)
  • add: Create layers relative to rootDir (67b9dab)
❤️ Contributors

v3.26.4

Compare Source

3.26.4 is the next patch release.

Timetable: to be announced.

👉 Changelog

compare changes

🩹 Fixes
  • dev: Await devServer.close (0d9ab2c)
  • dev: Add exception handlers for initial restart (#​975)
❤️ Contributors

v3.26.3

Compare Source

3.26.3 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes
  • dev: Only close config watchers when process exits (#​971)
  • dev: Call close watchers when cleaning up init (#​972)
  • dev: Work around rollup build bug (ef541a6)
  • dev: Expose port/host to options.devServer (#​970)
  • dev: Use get-port-please to handle socket paths (#​973)
  • dev: Use 'SIGTERM' to kill process on deno (#​974)
🤖 CI
  • Do not fail fast in matrix (fc146d1)
❤️ Contributors

v3.26.2

Compare Source

3.26.2 is the next patch release.

Timetable: to be announced.

👉 Changelog

compare changes

🩹 Fixes
  • Update default template name to v4 (beb7fb4)
❤️ Contributors

v3.26.1

Compare Source

3.26.1 is the next patch release.

Timetable: to be announced.

👉 Changelog

compare changes

🩹 Fixes
  • dev: Temporarily refactor to use previous socket url handling (#​957)
💅 Refactors
  • Simplify formatSocketURL logic (11330aa)
❤️ Contributors

v3.26.0

Compare Source

3.26.0 is the next minor release.

👀 Highlights

Nuxt CLI v3.26 focuses on performance with faster cold starts, intelligent caching, and architectural improvements that prepare the foundation for Nuxt v4. I very much hope it will make your dev workflow noticeably faster and more responsive.

I'm hoping to write up a little bit more about how we did this, but the key changes include:

🚀 Faster Development Server

Starting your Nuxt development server is now significantly faster. We've optimized the initialization sequence to prioritize critical operations and reduce startup time, especially noticeable in larger projects (#​902).

🔥 Node.js Compile Cache

The Node.js compile cache is now enabled automatically when supported, providing up to 3x faster startup times for subsequent CLI operations (#​911).

### first run: normal CLI load time
nuxt build

### ⚡ cached load
nuxt build 

The CLI automatically detects support and falls back gracefully when not available. (You can also set NODE_DISABLE_COMPILE_CACHE=1 to disable it.)

📁 Native File Watching

File watching now uses native fs.watch APIs for watching configuration files, .env, and the dist directory. This provides faster feedback and uses fewer system resources (#​913).

🔌 Socket-Based Development Proxy

The Nuxt dev server uses an internal connection between the host/port that the CLI starts, and the actual dev server. Previously, we used an internal TCP/IP network port, which had extra overhead, particularly on Windows machines. Now, where supported (currently Nuxt v4 only), we use a socket (#​921).

You can also test this with Nuxt v3 by setting the NUXT_SOCKET environment variable, but until v3.18 is released, this may actually slow down your dev server as the current Nuxt v3 vite-node dev server does not support sockets and will fall back to the public network interface.

⚡ Faster TypeScript Support

TypeScript resolution now happens in parallel with Nuxt type preparation, reducing nuxt typecheck times. The CLI also supports TypeScript project references, making it easier to work with monorepos (this also prepares for enhanced TypeScript integration in Nuxt v4) (#​928).

🛠️ Layer Support with --extends

Create new Nuxt projects that extend existing layers with the new --extends option (#​933):

nuxt dev --extends @​my-org/nuxt-layer my-project

It's advised instead to include the layer you extend in your nuxt.config file but this can be considered an escape hatch for situations where this is not possible.

🎯 Better Module Management

The nuxt init command now provides a cleaner module selection experience. Modules that are dependencies of other modules are automatically hidden, and you can skip module selection entirely with --no-modules.

We plan to improve this further in the next release with #​910.

🔧 Stability Improvements

This release comes with plenty of bug fixes, of course, as well as prioritising the version of @nuxt/kit actually used by the version of Nuxt you have installed. (This should fix some edge cases issues where the CLI was using a different version of @nuxt/kit than Nuxt itself.)

👉 Changelog

compare changes

🚀 Enhancements
  • dev: Add debug timing log (9d4da0b)
  • typecheck: Support ts projects (#​928)
  • Add --extends option to allow extending nuxt layers (#​933)
🔥 Performance
  • dev: Improve cold start of dev server (#​902)
  • Enable node compile cache (#​911)
  • dev: Use native fs.watch to watch dist, config and .env (#​913)
  • typecheck: Resolve typescript alongside preparing nuxt types (b3229ed)
  • dev: Use socket to proxy connections to dev server (#​921)
  • dev: Use exsolve to resolve + import legacy loading template (#​936)
🩹 Fixes
  • init: Allow skipping modules prompt with --no-modules (#​888)
  • init: Ask before showing modules selector (#​895)
  • init: Skip modules that are dependencies of other modules (#​879)
  • module: Fix parsing bug for .npmrc files with comments (#​881)
  • Correctly polyfill globalThis.crypto (29ddb60)
  • dev: Always create dist dir before watching it (cafc1ad)
  • Prioritise @​nuxt/kit from nuxt dependencies (#​929)
  • dev: Avoid recursive fs watching (2fc475b)
  • dev: Set xfwd headers (#​931)
  • Only set NODE_COMPILE_CACHE if cache can be enabled (a4827d2)
  • dev: Ensure we listen on port if _PORT is set (#​940)
  • typecheck: Proxy overrides to loadNuxt (#​942)
  • dev: Handle undefined process.title (#​946)
  • dev: Don't use sockets if provider is stackblitz (#​949)
💅 Refactors
  • dev: Directly emit address (+ type server) (f2e098a)
  • dev: Use get-port-please to produce socket addresses (#​952)
🏡 Chore
✅ Tests
  • Switch from deprecated vitest syntax (b6553eb)
  • Add dev server benchmarks (#​901)
  • Accurately benchmark forked mode (#​903)
  • Close servers (#​904)
  • Add additional e2e command tests (#​935)
🤖 CI
  • Run tests on macos as well (3ff4670)
  • Run tests against node 20 (b77626a)
  • Remove forced corepack installation (7fa1adc)
❤️ Contributors
nuxt/eslint (@​nuxt/eslint)

v1.9.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.8.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.7.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.7.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.6.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
microsoft/playwright (@​playwright/test)

v1.55.1

Compare Source

Highlights

#​37479 - [Bug]: Upgrade Chromium to 140.0.7339.186.
#​37147 - [Regression]: Internal error: step id not found.
#​37146 - [Regression]: HTML reporter displays a broken chip link when there are no projects.
#​37137 - Revert "fix(a11y): track inert elements as hidden".

Browser Versions

  • Chromium 140.0.7339.186
  • Mozilla Firefox 141.0
  • WebKit 26.0

This version was also tested against the following stable channels:

  • Google Chrome 139
  • Microsoft Edge 139

v1.55.0

Compare Source

v1.54.2

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/36714 - [Regression]: Codegen is not able to launch in Administrator Terminal on Windows (ProtocolError: Protocol error)https://github.com/microsoft/playwright/issues/368288 - [Regression]: Playwright Codegen keeps spamming with selected optiohttps://github.com/microsoft/playwright/issues/3681010 - [Regression]: Starting Codegen with target language doesn't work anymore

Browser Versions

  • Chromium 139.0.7258.5
  • Mozilla Firefox 140.0.2
  • WebKit 26.0

This version was also tested against the following stable channels:

  • Google Chrome 140
  • Microsoft Edge 140

v1.54.1

Compare Source

v1.54.0

Compare Source

Highlights

  • New cookie property partitionKey in browserContext.cookies() and browserContext.addCookies(). This property allows to save and restore partitioned cookies. See CHIPS MDN article for more information. Note that browsers have different support and defaults for cookie partitioning.

  • New option noSnippets to disable code snippets in the html report.

    import { defineConfig } from '@​playwright/test';
    
    export default defineConfig({
      reporter: [['html', { noSnippets: true }]]
    });
  • New property location in test annotations, for example in testResult.annotations and testInfo.annotations. It shows where the annotation like test.skip or test.fixme was added.

Command Line

  • New option --user-data-dir in multiple commands. You can specify the same user data dir to reuse browsing state, like authentication, between sessions.

    npx playwright codegen --user-data-dir=./user-data
  • Option -gv has been removed from the npx playwright test command. Use --grep-invert instead.

  • npx playwright open does not open the test recorder anymore. Use npx playwright codegen instead.

Miscellaneous

  • Support for Node.js 16 has been removed.
  • Support for Node.js 18 has been deprecated, and will be removed in the future.

Browser Versions

  • Chromium 139.0.7258.5
  • Mozilla Firefox 140.0.2
  • WebKit 26.0

This version was also tested against the following stable channels:

  • Google Chrome 140
  • Microsoft Edge 140
danielroe/provenance-action (danielroe/provenance-action)

v0.1.1

Compare Source

compare changes

🚀 Enhancements
  • Add support for bun.lock (#​12)
📖 Documentation
  • Use @main constraint for example (237ceea)
❤️ Contributors
eslint/eslint (eslint)

v9.36.0

Compare Source

v9.35.0

Compare Source

v9.34.0

Compare Source

v9.33.0

Compare Source

v9.32.0

Compare Source

v9.31.0

Compare Source

unjs/pkg-types (pkg-types)

v2.3.0

Compare Source

compare changes

🚀 Enhancements
  • packagejson: Object format support for workspaces field (#​236)
  • Add deno.lock to known lockfiles (#​244)
  • Support package.json5 and package.yaml (#​234)
  • updatePackage, sortPackage and normalizePackage utils (#​240)
🏡 Chore
❤️ Contributors
pnpm/pnpm (pnpm)

v10.17.1

Compare Source

Patch Changes
  • When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #​9974.
  • Fix state.json creation path when executing pnpm patch in a workspace project #​9733.
  • When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #​9987.

v10.17.0

Compare Source

Minor Changes
  • The minimumReleaseAgeExclude setting now supports patterns. For instance:

    minimumReleaseAge: 1440
    minimumReleaseAgeExclude:
      - "@​eslint/*"

    Related PR: #​9984.

Patch Changes
  • Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #​9978.
  • When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #​9979.

v10.16.1

Compare Source

Patch Changes
  • The full metadata cache should be stored not at the same location as the abbreviated metadata. This fixes a bug where pnpm was loading the abbreviated metadata from cache and couldn't find the "time" field as a result #​9963.
  • Forcibly disable ANSI color codes when generating patch diff #​9914.

v10.16.0

Compare Source

Minor Changes
  • There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.

    The new setting is called minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, setting minimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

    If you set minimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under the minimumReleaseAgeExclude setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:

    minimumReleaseAgeExclude:
      - webpack

    Related issue: #​9921.

  • Added support for finders #​9946.

    In the past, pnpm list and pnpm why could only search for dependencies by name (and optionally version). For example:

    pnpm why minimist
    

    prints the chain of dependencies to any installed instance of minimist:

    verdaccio 5.20.1
    ├─┬ handlebars 4.7.7
    │ └── minimist 1.2.8
    └─┬ mv 2.1.1
      └─┬ mkdirp 0.5.6
        └── minimist 1.2.8
    

    What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have react@17 in their peer dependencies?

    This is now possible with "finder functions". Finder functions can be declared in .pnpmfile.cjs and invoked with the --find-by=<function name> flag when running pnpm list or pnpm why.

    Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our .pnpmfile.cjs:

    module.exports = {
      finders: {
        react17: (ctx) => {
          return ctx.readManifest().peerDependencies?.react === "^17.0.0";
        },
      },
    };

    Now we can use this finder function by running:

    pnpm why --find-by=react17
    

    pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.

    @&#8203;apollo/client 4.0.4
    ├── @&#8203;graphql-typed-document-node/core 3.2.0
    └── graphql-tag 2.12.6
    

    It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:

    module.exports = {
      finders: {
        react17: (ctx) => {
          const manifest = ctx.readManifest();
          if (manifest.peerDependencies?.react === "^17.0.0") {
            return `license: ${manifest.license}`;
          }
          return false;
        },
      },
    };

    Every matched package will also print out the license from its package.json:

    @&#8203;apollo/client 4.0.4
    ├── @&#8203;graphql-typed-document-node/core 3.2.0
    │   license: MIT
    └── graphql-tag 2.12.6
        license: MIT
    
Patch Changes
  • Fix deprecation warning printed when executing pnpm with Node.js 24 #​9529.
  • Throw an error if nodeVersion is not set to an exact semver version #​9934.
  • pnpm publish should be able to publish a .tar.gz file #​9927.
  • Canceling a running process with Ctrl-C should make pnpm run return a non-zero exit code #​9626.

v10.15.1

Compare Source

Patch Changes
  • Fix .pnp.cjs crash when importing subpath #​9904.
  • When resolving peer dependencies, pnpm looks whether the peer dependency is present in the root workspace project's dependencies. This change makes it so that the peer dependency is correctly resolved even from aliased npm-hosted dependencies or other types of dependencies #​9913.

v10.15.0

Compare Source

Minor Changes
  • Added the cleanupUnusedCatalogs configuration. When set to true, pnpm will remove unused catalog entries during installation #​9793.
  • Automatically load pnpmfiles from config dependencies that are named @*/pnpm-plugin-* #​9780.
  • pnpm config get now prints an INI string for an object value #​9797.
  • pnpm config get now accepts property paths (e.g. pnpm config get catalog.react, pnpm config get .catalog.react, pnpm config get 'packageExtensions["@&#8203;babel/parser"].peerDependencies["@&#8203;babel/types"]'), and pnpm config set now accepts dot-leading or subscripted keys (e.g. pnpm config set .ignoreScripts true).
  • pnpm config get --json now prints a JSON serialization of config value, and pnpm config set --json now parses the input value as JSON.
Patch Changes
  • Semi-breaking. When automatically installing missing peer dependencies, prefer versions that are already present in the direct dependencies of the root workspace package #​9835.
  • When executing the pnpm create command, must verify whether the node version is supported even if a cache already exists #​9775.
  • When making requests for the non-abbreviated packument, add */* to the Accept header to avoid getting a 406 error on AWS CodeArtifact #​9862.
  • The standalone exe version of pnpm works with glibc 2.26 again #​9734.
  • Fix a regression in which pnpm dlx pkg --help doesn't pass --help to pkg #​9823.

v10.14.0

Compare Source

Minor Changes
  • Added support for JavaScript runtime resolution

    Declare Node.js, Deno, or Bun in devEngines.runtime (inside package.json) and let pnpm download and pin it automatically.

    Usage example:

    {
      "devEngines": {
        "runtime": {
          "name": "node",
          "version": "^24.4.0",
          "onFail": "download" (we only support the "download" value for now)
        }
      }
    }

    How it works:

    1. pnpm install resolves your specified range to the latest matching runtime version.
    2. The exact version (and checksum) is saved in the lockfile.
    3. Scripts use the local runtime, ensuring consistency across environments.

    Why this is better:

    1. This new setting supports also Deno and Bun (vs. our Node-only settings useNodeVersion and executionEnv.nodeVersion)
    2. Supports version ranges (not just a fixed version).
    3. The resolved version is stored in the pnpm lockfile, along with an integrity checksum for future validation of the Node.js content's validity.
    4. It can be used on any workspace project (like executionEnv.nodeVersion). So, different projects in a workspace can use different runtimes.
    5. For now devEngines.runtime setting will install the runtime locally, which we will improve in future versions of pnpm by using a shared location on the computer.

    Related PR: #​9755.

  • Add --cpu, --libc, and --os to pnpm install, pnpm add, and pnpm dlx to customize supportedArchitectures via the CLI #​7510.

Patch Changes
  • Fix a bug in which pnpm add downloads packages whose libc differ from pnpm.supportedArchitectures.libc.
  • The integrities of the downloaded Node.js artifacts are verified #​9750.
  • Allow dlx to parse CLI flags and options between the dlx command and the command to run or between the dlx command and -- #​9719.
  • pnpm install --prod should removing hoisted dev dependencies #​9782.
  • Fix an edge case bug causing local tarballs to not re-link into the virtual store. This bug would happen when changing the contents of the tarball without renaming the file and running a filtered install.
  • Fix a bug causing pnpm install to incorrectly assume the lockfile is up to date after changing a local tarball that has peers dependencies.

v10.13.1

Compare Source

Patch Changes
  • Run user defined pnpmfiles after pnpmfiles of plugins.

v10.13.0

Compare Source

Minor Changes
  • Added the possibility to load multiple pnpmfiles. The pnpmfile setting can now accept a list of pnpmfile locations #​9702.

  • pnpm will now automatically load the pnpmfile.cjs file from any config dependency named @pnpm/plugin-* or pnpm-plugin-* #​9729.

    The order in which config dependencies are initialized should not matter — they are initialized in alphabetical order. If a specific order is needed, the paths to the pnpmfile.cjs files in the config dependencies can be explicitly listed using the pnpmfile setting in pnpm-workspace.yaml.

Patch Changes
  • When patching dependencies installed via pkg.pr.new, treat them as Git tarball URLs #​9694.
  • Prevent conflicts between local projects' config and the global config in dangerouslyAllowAllBuilds, onlyBuiltDependencies, onlyBuiltDependenciesFile, and neverBuiltDependencies #​9628.
  • Sort keys in pnpm-workspace.yaml with deep #​9701.
  • The pnpm rebuild command should not add pkgs included in ignoredBuiltDependencies to ignoredBuilds in node_modules/.modules.yaml #​9338.
  • Replaced shell-quote with shlex for quoting command arguments #​9381.
tailwindlabs/tailwindcss (tailwindcss)

v4.1.13

Compare Source

Changed
  • Drop warning from browser build (#​18731)
  • Drop exact duplicate declarations when emitting CSS (#​18809)
Fixed
  • Don't transition visibility when using transition (#​18795)
  • Discard matched variants with unknown named values (#​18799)
  • Discard matched variants with non-string values (#​18799)
  • Show suggestions for known matchVariant values (#​18798)
  • Replace deprecated clip with clip-path in sr-only (#​18769)
  • Hide internal fields from completions in matchUtilities (#​18820)
  • Ignore .vercel folders by default (can be overridden by @source … rules) (#​18855)
  • Consider variants starting with @- to be invalid (e.g. @-2xl:flex) (#​18869)
  • Do not allow custom variants to start or end with a - or _ (#​18867, #​18872)
  • Upgrade: Migrate aria theme keys to @custom-variant (#​18815)
  • Upgrade: Migrate data theme keys to @custom-variant (#​18816)
  • Upgrade: Migrate supports theme keys to @custom-variant (#​18817)

v4.1.12

Compare Source

Fixed
  • Don't consider the global important state in @apply (#​18404)
  • Add missing suggestions for flex-<number> utilities (#​18642)
  • Fix trailing ) from interfering with extraction in Clojure keywords (#​18345)
  • Detect classes inside Elixir charlist, word list, and string sigils (#​18432)
  • Track source locations through @plugin and @config (#​18345)
  • Allow boolean values of process.env.DEBUG in @tailwindcss/node (#​18485)
  • Ignore consecutive semicolons in the CSS parser (#​18532)
  • Center the dropdown icon added to an input with a paired datalist by default (#​18511)
  • Extract candidates in Slang templates (#​18565)
  • Improve error messages when encountering invalid functional utility names (#​18568)
  • Discard CSS AST objects with false or undefined properties (#​18571)
  • Allow users to disable URL rebasing in @tailwindcss/postcss via transformAssetUrls: false (#​18321)
  • Fix false-positive migrations in addEventListener and JavaScript variable names (#​18718)
  • Fix Standalone CLI showing default Bun help when run via symlink on Windows (#​18723)
  • Read from --border-color-* theme keys in divide-* utilities for backwards compatibility (#​18704)
  • Don't scan .hdr and .exr files for classes by default (#​18734)
SuperchupuDev/tinyglobby (tinyglobby)

v0.2.15

Compare Source

Added
  • Documentation page at https://superchupu.dev/tinyglobby,
    which also contains a library comparison page and migration guide.

    It's been a huge effort that took two months to make.

    Big thanks to outslept, 43081j
    and benmccann for helping out! ❤️

  • JSDoc to all functions and options based on the online documentation page

  • Benchmarks with help from
    43081j and benmccann

  • braceExpansion option

  • extglob option

  • fs option

  • globstar option by benmccann

  • signal option

  • package.json export as tinyglobby/package.json

  • Ability to pass readonly types by TomerAberbach

  • Support for URLs in cwd option

Changed
  • Rewritten path processing algorithm leading to a huge performance increase in many cases
    with help from 43081j and benmccann

  • Deprecated using patterns inside the options object

  • Enabled trusted publishing using npm's OIDC support

Fixed
  • Negated bracket expressions i.e. [!abc]
  • Some patterns like +++ breaking the partial matcher
vercel/turborepo (turbo)

v2.5.7

Compare Source

v2.5.6: Turborepo v2.5.6

Compare Source

What's Changed

Docs

Configuration

📅 Schedule: Branch creation - "on Monday" (UTC), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR is behind base branch, 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 requested a review from danielroe as a code owner July 28, 2025 15:09
Copy link

vercel bot commented Jul 28, 2025

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

Project Deployment Preview Comments Updated (UTC)
examples Ready Ready Preview Comment Sep 23, 2025 4:21pm

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9c62af2 to 6e94182 Compare July 29, 2025 21:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6e94182 to 896697a Compare July 30, 2025 07:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 896697a to bae8ff3 Compare July 31, 2025 23:07
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from bae8ff3 to 09ea81d Compare August 1, 2025 08:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 09ea81d to 403baba Compare August 1, 2025 17:26
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 403baba to 6357b2b Compare August 2, 2025 10:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6357b2b to 0b1c475 Compare August 6, 2025 09:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0b1c475 to 4bc3f01 Compare August 7, 2025 05:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4bc3f01 to 2ce5129 Compare August 8, 2025 17:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2ce5129 to 97b5eb0 Compare August 8, 2025 21:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 97b5eb0 to 1a311a0 Compare August 10, 2025 09:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1a311a0 to 8295e5b Compare August 10, 2025 15:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8295e5b to 5caf2de Compare August 10, 2025 19:44
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5caf2de to ab06501 Compare August 10, 2025 22:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3c237d7 to 0fe3d03 Compare September 16, 2025 00:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0fe3d03 to 12f1119 Compare September 16, 2025 21:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 12f1119 to 88f878a Compare September 17, 2025 03:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 88f878a to 2b0acb6 Compare September 17, 2025 06:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2b0acb6 to 279fa63 Compare September 17, 2025 12:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 279fa63 to 87b640a Compare September 17, 2025 16:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 87b640a to 7633155 Compare September 18, 2025 03:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7633155 to 63843b7 Compare September 18, 2025 19:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 63843b7 to cd795a2 Compare September 19, 2025 15:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cd795a2 to bcc37e7 Compare September 22, 2025 08:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from bcc37e7 to fa37040 Compare September 22, 2025 15:09
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fa37040 to f158ff7 Compare September 22, 2025 19:07
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f158ff7 to 888d7d0 Compare September 23, 2025 11:42
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