Skip to content

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

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 11, 2025
Merged

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

merged 1 commit into from
Jun 11, 2025

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 22, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@nuxt/eslint-config (source) ^1.2.0 -> ^1.4.1 age adoption passing confidence devDependencies minor
@nuxt/test-utils ^3.17.2 -> ^3.19.1 age adoption passing confidence devDependencies minor
actions/setup-node v4.3.0 -> v4.4.0 age adoption passing confidence action minor
crawler-user-agents ^1.2.0 -> ^1.15.0 age adoption passing confidence devDependencies minor
eslint (source) ^9.22.0 -> ^9.28.0 age adoption passing confidence devDependencies minor
happy-dom ^17.4.4 -> ^17.6.3 age adoption passing confidence devDependencies minor
playwright (source) ^1.51.1 -> ^1.53.0 age adoption passing confidence devDependencies minor
pnpm (source) 10.6.5 -> 10.12.1 age adoption passing confidence packageManager minor
typescript (source) ^5.8.2 -> ^5.8.3 age adoption passing confidence devDependencies patch
vitest (source) ^3.0.9 -> ^3.2.3 age adoption passing confidence devDependencies minor

Release Notes

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

v1.4.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.4.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.3.1

Compare Source

No significant changes

    View changes on GitHub

v1.3.0

Compare Source

   🚀 Features
    View changes on GitHub
nuxt/test-utils (@​nuxt/test-utils)

v3.19.1

Compare Source

👉 Changelog

compare changes

🩹 Fixes
  • config: Upgrade nuxt devtools + disable vue devtools (#​824)
  • module: Import defineConfig from vite (467886ea)
🏡 Chore
  • Don't ignore @nuxt/devtools upgrade (3ae47b43)
❤️ Contributors

v3.19.0

Compare Source

👉 Changelog

compare changes

🚀 Enhancements
  • config: Support vitest workspaces with defineVitestProject (#​1258)
  • config: Add nuxt environment browser-testing support (#​1294)
🩹 Fixes
  • config: Use UserConfig rather than InlineConfig from vite (e2a1598b)
💅 Refactors
  • Rename core -> e2e internally (a81c4498)
✅ Tests
  • Set environment: 'nuxt' for browser testing example (96769e55)
  • Add browser mode tests for nuxt/content components (#​1284)
❤️ Contributors

v3.18.0

Compare Source

compare changes

🚀 Enhancements
  • e2e: Add support for bun test runner (#​1264)
  • config: Support vitest browser mode (#​1271)
🩹 Fixes
  • vitest-environment: Respect custom app.baseURL in manifest path (#​1213)
  • runtime-utils: Wrap WrapperComponent default slot in function (#​1244)
💅 Refactors
  • Rename setup hook to beforeAll for clarity (#​1221)
📖 Documentation
✅ Tests
❤️ Contributors
actions/setup-node (actions/setup-node)

v4.4.0

Compare Source

What's Changed

Bug fixes:
Enhancement:
Dependency update:

New Contributors

Full Changelog: actions/setup-node@v4...v4.4.0

monperrus/crawler-user-agents (crawler-user-agents)

v1.15.0

Compare Source

v1.14.0

Compare Source

v1.13.0

Compare Source

v1.12.0

Compare Source

v1.11.0

Compare Source

v1.10.0

Compare Source

v1.9.0

Compare Source

v1.8.0

Compare Source

v1.7.0

Compare Source

v1.6.0

Compare Source

v1.5.0

Compare Source

v1.4.0

Compare Source

v1.3.0

Compare Source

eslint/eslint (eslint)

v9.28.0

Compare Source

v9.27.0

Compare Source

v9.26.0

Compare Source

v9.25.1

Compare Source

v9.25.0

Compare Source

v9.24.0

Compare Source

v9.23.0

Compare Source

capricorn86/happy-dom (happy-dom)

v17.6.3

Compare Source

👷‍♂️ Patch fixes

v17.6.2

Compare Source

👷‍♂️ Patch fixes

v17.6.1

Compare Source

🎨 Features
  • Adds support for disabling validation of certificates, to allow for self-signed certificates to be used - By @​capricorn86 in task #​1763
    • Read more about the new setting fetch.disableStrictSSL under IBrowserSettings in the Wiki

v17.6.0

Compare Source

v17.5.9

Compare Source

👷‍♂️ Patch fixes
  • Adds missing null check in HTMLLinkElement for a browser frame property that becomes null during teardown of a Window - By @​capricorn86 in task #​1800

v17.5.8

Compare Source

👷‍♂️ Patch fixes
  • Incorrect cache matching caused Element.classList to return the wrong items - By @​capricorn86 in task #​1812

v17.5.7

Compare Source

👷‍♂️ Patch fixes
  • Handle wider range of valid characters in unquoted attribute value parsing - By @​AudunWA in task #​1817

v17.5.6

Compare Source

👷‍♂️ Patch fixes
  • Removes the min and max boundary check when setting the value of an input field of type "date" - By @​zgrybus in task #​1815

v17.5.5

Compare Source

v17.5.4

Compare Source

👷‍♂️ Patch fixes

v17.5.3

Compare Source

👷‍♂️ Patch fixes
  • Adds previousSibling and nextSibling to MutationObserver records when a child is removed - By @​uxuip in task #​1803

v17.5.2

Compare Source

v17.5.1

Compare Source

👷‍♂️ Patch fixes
  • Existing URL query string should be overwritten on form submit when method is "GET" - By @​rslabbert in task #​1786

v17.5.0

Compare Source

🎨 Features

v17.4.9

Compare Source

v17.4.8

Compare Source

👷‍♂️ Patch fixes

v17.4.7

Compare Source

👷‍♂️ Patch fixes

v17.4.6

Compare Source

👷‍♂️ Patch fixes

v17.4.5

Compare Source

👷‍♂️ Patch fixes
microsoft/playwright (playwright)

v1.53.0

Compare Source

Trace Viewer and HTML Reporter Updates

  • New Steps in Trace Viewer and HTML reporter: New Trace Viewer Steps

  • New option in 'html' reporter to set the title of a specific test run:

    import { defineConfig } from '@​playwright/test';

export default defineConfig({
  reporter: [['html', { title: 'Custom test run #​1028' }]]
});

Miscellaneous

  • New option kind in testInfo.snapshotPath() controls which snapshot path template is used.

  • New method locator.describe() to describe a locator. Used for trace viewer and reports.

    const button = page.getByTestId('btn-sub').describe('Subscribe button');
await button.click();

  • npx playwright install --list will now list all installed browsers, versions and locations.

Browser Versions

  • Chromium 138.0.7204.4
  • Mozilla Firefox 139.0
  • WebKit 18.5

This version was also tested against the following stable channels:

  • Google Chrome 137
  • Microsoft Edge 137

v1.52.0

Compare Source

pnpm/pnpm (pnpm)

v10.12.1

Minor Changes

  • Experimental. Added support for global virtual stores. When enabled, node_modules contains only symlinks to a central virtual store, rather to node_modules/.pnpm. By default, this central store is located at <store-path>/links (you can find the store path by running pnpm store path).

    In the central virtual store, each package is hard linked into a directory whose name is the hash of its dependency graph. This allows multiple projects on the system to symlink shared dependencies from this central location, significantly improving installation speed when a warm cache is available.

    This is conceptually similar to how NixOS manages packages, using dependency graph hashes to create isolated and reusable package directories.

    To enable the global virtual store, set enableGlobalVirtualStore: true in your root pnpm-workspace.yaml, or globally via:

    pnpm config -g set enable-global-virtual-store true

    NOTE: In CI environments, where caches are typically cold, this setting may slow down installation. pnpm automatically disables the global virtual store when running in CI.

    Related PR: #​8190

  • The pnpm update command now supports updating catalog: protocol dependencies and writes new specifiers to pnpm-workspace.yaml.
  • Added two new CLI options (--save-catalog and --save-catalog-name=<name>) to pnpm add to save new dependencies as catalog entries. catalog: or catalog:<name> will be added to package.json and the package specifier will be added to the catalogs or catalog[<name>] object in pnpm-workspace.yaml #​9425.
  • Semi-breaking. The keys used for side-effects caches have changed. If you have a side-effects cache generated by a previous version of pnpm, the new version will not use it and will create a new cache instead #​9605.
  • Added a new setting called ci for explicitly telling pnpm if the current environment is a CI or not.
Patch Changes
  • Sort versions printed by pnpm patch using semantic versioning rules.
  • Improve the way the error message displays mismatched specifiers. Show differences instead of 2 whole objects #​9598.
  • Revert #​9574 to fix a regression #​9596.

v10.11.1

Compare Source

Patch Changes
  • Fix an issue in which pnpm deploy --legacy creates unexpected directories when the root package.json has a workspace package as a peer dependency #​9550.
  • Dependencies specified via a URL that redirects will only be locked to the target if it is immutable, fixing a regression when installing from GitHub releases. (#​9531)
  • Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #​9505.
  • Use pnpm_config_ env variables instead of npm_config_ #​9571.
  • Fix a regression (in v10.9.0) causing the --lockfile-only flag on pnpm update to produce a different pnpm-lock.yaml than an update without the flag.
  • Let pnpm deploy work in repos with overrides when inject-workspace-packages=true #​9283.
  • Fixed the problem of path loss caused by parsing URL address. Fixes a regression shipped in pnpm v10.11 via #​9502.
  • pnpm -r --silent run should not print out section #​9563.

v10.11.0

Compare Source

Minor Changes

  • A new setting added for pnpm init to create a package.json with type=module, when init-type is module. Works as a flag for the init command too #​9463.

  • Added support for Nushell to pnpm setup #​6476.

  • Added two new flags to the pnpm audit command, --ignore and --ignore-unfixable #​8474.

    Ignore all vulnerabilities that have no solution:

    > pnpm audit --ignore-unfixable

    Provide a list of CVE's to ignore those specifically, even if they have a resolution.

    > pnpm audit --ignore=CVE-2021-1234 --ignore=CVE-2021-5678

  • Added support for recursively running pack in every project of a workspace #​4351.

    Now you can run pnpm -r pack to pack all packages in the workspace.

Patch Changes
  • pnpm version management should work, when dangerouslyAllowAllBuilds is set to true #​9472.
  • pnpm link should work from inside a workspace #​9506.
  • Set the default workspaceConcurrency to Math.min(os.availableParallelism(), 4) #​9493.
  • Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #​9505.
  • Read updateConfig from pnpm-workspace.yaml #​9500.
  • Add support for recursive pack
  • Remove url.parse usage to fix warning on Node.js 24 #​9492.
  • pnpm run should be able to run commands from the workspace root, if ignoreScripts is set tot true #​4858.

v10.10.0

Compare Source

Minor Changes
  • Allow loading the preResolution, importPackage, and fetchers hooks from local pnpmfile.
Patch Changes
  • Fix cd command, when shellEmulator is true #​7838.
  • Sort keys in pnpm-workspace.yaml #​9453.
  • Pass the npm_package_json environment variable to the executed scripts #​9452.
  • Fixed a mistake in the description of the --reporter=silent option.

v10.9.0

Compare Source

Minor Changes

  • Added support for installing JSR packages. You can now install JSR packages using the following syntax:

    pnpm add jsr:<pkg_name>

    or with a version range:

    pnpm add jsr:<pkg_name>@&#8203;<range>

    For example, running:

    pnpm add jsr:@&#8203;foo/bar

    will add the following entry to your package.json:

    {
  "dependencies": {
    "@&#8203;foo/bar": "jsr:^0.1.2"
  }
}

    When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:

    {
  "dependencies": {
    "@&#8203;foo/bar": "npm:@&#8203;jsr/foo__bar@^0.1.2"
  }
}

    Related issue: #​8941.

    Note: The @jsr scope defaults to https://npm.jsr.io/ if the @jsr:registry setting is not defined.

  • Added a new setting, dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this to pnpm-workspace.yaml:

    neverBuiltDependencies: []

    dangerouslyAllowAllBuilds has the same effect but also allows to be set globally via:

    pnpm config set dangerouslyAllowAllBuilds true

    It can also be set when running a command:

    pnpm install --dangerously-allow-all-builds
Patch Changes
  • Fix a false negative in verifyDepsBeforeRun when nodeLinker is hoisted and there is a workspace package without dependencies and node_modules directory #​9424.
  • Explicitly drop verifyDepsBeforeRun support for nodeLinker: pnp. Combining verifyDepsBeforeRun and nodeLinker: pnp will now print a warning.

v10.8.1

Compare Source

Patch Changes
  • Removed bright white highlighting, which didn't look good on some light themes #​9389.
  • If there is no pnpm related configuration in package.json, onlyBuiltDependencies will be written to pnpm-workspace.yaml file #​9404.

v10.8.0

Compare Source

Minor Changes

  • Experimental. A new hook is supported for updating configuration settings. The hook can be provided via .pnpmfile.cjs. For example:

    module.exports = {
  hooks: {
    updateConfig: (config) => ({
      ...config,
      nodeLinker: "hoisted",
    }),
  },
};

  • Now you can use the pnpm add command with the --config flag to install new configurational dependencies #​9377.

Patch Changes
  • Do not hang indefinitely, when there is a glob that starts with !/ in pnpm-workspace.yaml. This fixes a regression introduced by #​9169.
  • pnpm audit --fix should update the overrides in pnpm-workspace.yaml.
  • pnpm link should update overrides in pnpm-workspace.yaml, not in package.json #​9365.

v10.7.1: pnpm 10.7.1

Compare Source

Patch Changes

  • pnpm config set should convert the settings to their correct type before adding them to pnpm-workspace.yaml #​9355.
  • pnpm config get should read auth related settings via npm CLI #​9345.
  • Replace leading ~/ in a path in .npmrc with the home directory #​9217.

Platinum Sponsors

Bit Bit Syntax

Gold Sponsors

Discord u|screen
JetBrains Nx
CodeRabbit Route4Me
Workleap Stackblitz

v10.7.0

Compare Source

Minor Changes

  • pnpm config get and list also show settings set in pnpm-workspace.yaml files #​9316.

  • It should be possible to use env variables in pnpm-workspace.yaml setting names and value.

  • Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

    For example:

    patchedDependencies:
  foo: patches/foo-1.patch
  foo@^2.0.0: patches/foo-2.patch
  [email protected]: patches/foo-3.patch

    The above configuration would apply patches/foo-3.patch to [email protected], patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.

    [!WARNING]
    The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:

    # pnpm-workspace.yaml
patchedDependencies:
  # the specialized sub range
  '[email protected]': patches/foo.2.2.0-2.8.0.patch
  # the more general patch, excluding the sub range above
  'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch

    In most cases, however, it's sufficient to just define an exact version to override the range.

  • pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #​9316.

  • Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.

  • Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

    If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

    If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

    If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes
  • Remove dependency paths from audit output to prevent out-of-memory errors #​9280.
microsoft/TypeScript (typescript)

v5.8.3

Compare Source

vitest-dev/vitest (vitest)

v3.2.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.2.0

Compare Source

v3.1.4

[Compare Source](https://redirect.github.c

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 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 changed the title chore(deps): update devdependency eslint to ^9.23.0 chore(deps): update all non-major dependencies Mar 26, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 864c4b8 to c24c590 Compare April 2, 2025 09:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 4563e6e to 2261453 Compare April 11, 2025 16:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 92e1d79 to d757491 Compare April 18, 2025 20:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 2bc8f5b to e3824e8 Compare April 28, 2025 00:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from ad212f9 to 686a00f Compare May 3, 2025 16:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 7e8cbaa to 8a838c3 Compare May 12, 2025 04:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 0acfe06 to f92314b Compare May 20, 2025 05:24
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 2330ec6 to 44e8f37 Compare May 30, 2025 20:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from e5a475e to 04f106d Compare June 8, 2025 15:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 04f106d to 4d3745c Compare June 9, 2025 17:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4d3745c to 6664e39 Compare June 10, 2025 18:31
@DamianGlowala DamianGlowala merged commit 6f7567d into main Jun 11, 2025
2 checks passed
@DamianGlowala DamianGlowala deleted the renovate/all-minor-patch branch June 11, 2025 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

3.x chore

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@DamianGlowala