Skip to content

fix(deps): update minor dependencies #88

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 8, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nuxt/content (source) 3.4.0 -> 3.5.0 age adoption passing confidence
@nuxt/eslint (source) 1.2.0 -> 1.3.0 age adoption passing confidence
@tailwindcss/vite (source) 4.0.17 -> 4.1.4 age adoption passing confidence
eslint (source) 9.23.0 -> 9.25.1 age adoption passing confidence
pnpm (source) 10.6.1 -> 10.9.0 age adoption passing confidence
tailwindcss (source) 4.0.17 -> 4.1.4 age adoption passing confidence

Release Notes

nuxt/content (@​nuxt/content)

v3.5.0

Compare Source

Features
Bug Fixes
  • cache: split large queries (ef50925)
  • cloudflare: load sql dump from assets (#​3275) (453ba2e)
  • collection: avoid double update of some record by using the hash column as index (#​3304) (ebfb6e5)
  • dev: do not create hash column on local cache table (8fff15c)
  • Disallow crawlers from crawling /__nuxt_content paths. (#​3299) (849e79d)
  • explicitly set the dump's content type (#​3302) (e1a98d4)
  • generate correct collection insert for object and array default values (#​3277) (a9587ee)
  • module: invalid rootDir of layer sources (#​3308) (2579910)
  • preview: handle collection search with prefixed sources (#​3317) (c152782)
  • preview: handle strings format when generating insert query (c18e094)
  • preview: remove prefix when parsing files (498168f)
  • preview: transform value based on schema for sql query generation (994ae98)
  • reactively load components when body changes (#​3283) (b6a30aa)
  • templates: props definition (997fc65)
  • update csv docs & fix csv options typo (#​3300) (2c2fc77)
nuxt/eslint (@​nuxt/eslint)

v1.3.0

Compare Source

   🚀 Features
    View changes on GitHub
tailwindlabs/tailwindcss (@​tailwindcss/vite)

v4.1.4

Compare Source

Added
  • Add experimental @tailwindcss/oxide-wasm32-wasi target for running Tailwind in browser environments like StackBlitz (#​17558)
Fixed
  • Ensure color-mix(…) polyfills do not cause used CSS variables to be removed (#​17555)
  • Ensure color-mix(…) polyfills create fallbacks for theme variables that reference other theme variables (#​17562)
  • Fix brace expansion in declining ranges like {10..0..5} and {0..10..-5} (#​17591)
  • Work around a Chrome rendering bug when using the skew-* utilities (#​17627)
  • Ensure container query variant names can contain hyphens (#​17628)
  • Ensure shadow-inherit, inset-shadow-inherit, drop-shadow-inherit, and text-shadow-inherit inherit the shadow color (#​17647)
  • Ensure compatibility with array tuples used in fontSize JS theme keys (#​17630)
  • Ensure folders with binary file extensions in their names are scanned for utilities (#​17595)
  • Upgrade: Convert fontSize array tuple syntax to CSS theme variables (#​17630)

v4.1.3

Compare Source

Fixed
  • Show warning when using unsupported bare value data type in --value(…) (#​17464)
  • PostCSS: Ensure changes to the input CSS file don't generate stale output when using Turbopack (#​17554)
  • Ensure classes are detected in Ruby's %w syntax in Slim templates (#​17557)

v4.1.2

Compare Source

Fixed
  • Don't rely on the presence of @layer base to polyfill @property (#​17506)
  • Support setting multiple inset shadows as arbitrary values (#​17523)
  • Fix drop-shadow-* utilities that are defined with multiple shadows (#​17515)
  • PostCSS: Fix race condition when two changes are queued concurrently (#​17514)
  • PostCSS: Ensure files containing @tailwind utilities are processed (#​17514)
  • Ensure the color-mix(…) polyfill creates fallbacks even when using colors that cannot be statically analyzed (#​17513)
  • Fix slow incremental builds with @tailwindcss/vite and @tailwindcss/postscss (especially on Windows) (#​17511)
  • Vite: Fix missing CSS file in Qwik setups (#​17533)

v4.1.1

Compare Source

Fixed
  • Disable padding in @source inline(…) brace expansion (#​17491)
  • Inject polyfills after @import and body-less @layer (#​17493)
  • Ensure @tailwindcss/cli does not contain an import for jiti (#​17502)

v4.1.0

Compare Source

Added
  • Add details-content variant (#​15319)
  • Add inverted-colors variant (#​11693)
  • Add noscript variant (#​11929, #​17431)
  • Add items-baseline-last and self-baseline-last utilities (#​13888, #​17476)
  • Add pointer-none, pointer-coarse, and pointer-fine variants (#​16946)
  • Add any-pointer-none, any-pointer-coarse, and any-pointer-fine variants (#​16941)
  • Add safe alignment utilities (#​14607)
  • Add user-valid and user-invalid variants (#​12370)
  • Add wrap-anywhere, wrap-break-word, and wrap-normal utilities (#​12128)
  • Add @source inline(…) and @source not inline(…) (#​17147)
  • Add @source not "…" (#​17255)
  • Add text-shadow-* utilities (#​17389)
  • Add mask-* utilities (#​17134)
  • Add bg-{position,size}-* utilities for arbitrary values (#​17432)
  • Add shadow-*/<alpha>, inset-shadow-*/<alpha>, drop-shadow-*/<alpha>, and text-shadow-*/<alpha> utilities to control shadow opacity (#​17398, #​17434)
  • Add drop-shadow-<color> utilities (#​17434)
  • Improve compatibility with older versions of Safari and Firefox (#​17435)
Fixed
  • Follow symlinks when resolving @source directives (#​17391)
  • Don't scan ignored files for classes when changing an ignored file triggers a rebuild using @tailwindcss/cli (#​17255)
  • Support negated content rules in legacy JavaScript configuration (#​17255)
  • Interpret syntax like @("@&#8203;")md:… as @md:… in Razor files (#​17427)
  • Disallow top-level braces, top-level semicolons, and unbalanced parentheses and brackets in arbitrary values (#​17361)
  • Ensure the --theme(…) function still resolves to the CSS variables when using legacy JS plugins (#​17458)
  • Detect used theme variables in CSS module files (#​17433, #​17467)
Changed
  • Ignore node_modules by default (can be overridden by @source … rules) (#​17255)
  • @source rules that include file extensions or point inside node_modules/ folders no longer consider your .gitignore rules (#​17255)
  • Deprecate bg-{left,right}-{top,bottom} in favor of bg-{top,bottom}-{left,right} utilities (#​17378)
  • Deprecate object-{left,right}-{top,bottom} in favor of object-{top,bottom}-{left,right} utilities (#​17437)
eslint/eslint (eslint)

v9.25.1

Compare Source

v9.25.0

Compare Source

v9.24.0

Compare Source

pnpm/pnpm (pnpm)

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.

v10.6.5

Compare Source

v10.6.4: pnpm 10.6.4

Compare Source

Patch Changes

  • Fix pnpm dlx with --allow-build flag #​9263.
  • Invalid Node.js version in use-node-version should not cause pnpm itself to break #​9276.
  • The max amount of workers running for linking packages from the store has been reduced to 4 to achieve optimal results #​9286. The workers are performing many file system operations, so increasing the number of CPUs doesn't help performance after some point.

Platinum Sponsors

Bit Bit Syntax

Gold Sponsors

Discord u|screen
JetBrains Nx
CodeRabbit Route4Me
Workleap Stackblitz

v10.6.3

Compare Source

Patch Changes
  • pnpm install --prod=false should not crash, when executed in a project with a pnpm-workspace.yaml file #​9233. This fixes regression introduced via #​9211.

  • Add the missing node-options config to recursive run #​9180.

  • Removed a branching code path that only executed when dedupe-peer-dependents=false. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that override dedupe-peer-dependents to false. There should be less unique bugs from turning off dedupe-peer-dependents.

    See details in #​9259.

v10.6.2

Compare Source

Patch Changes
  • pnpm self-update should always update the version in the packageManager field of package.json.
  • Fix running pnpm CLI from pnpm CLI on Windows when the CLI is bundled to an executable #​8971.
  • pnpm patch-commit will now use the same filesystem as the store directory to compare and create patch files.
  • Don't show info output when --loglevel=error is used.
  • peerDependencyRules should be set in pnpm-workspace.yaml to take effect.

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 added the dependencies Pull requests that update a dependency file label Mar 8, 2025
@renovate renovate bot changed the title fix(deps): update dependency @nuxt/fonts to ^0.11.0 fix(deps): update minor dependencies Mar 12, 2025
@renovate renovate bot force-pushed the renovate/minor-dependencies branch 3 times, most recently from e17a000 to 29283d5 Compare March 15, 2025 15:22
@renovate renovate bot changed the title fix(deps): update minor dependencies fix(deps): update dependency @nuxt/fonts to ^0.11.0 Mar 15, 2025
@renovate renovate bot force-pushed the renovate/minor-dependencies branch from 29283d5 to 4ea04dc Compare March 18, 2025 22:03
@renovate renovate bot changed the title fix(deps): update dependency @nuxt/fonts to ^0.11.0 fix(deps): update minor dependencies Mar 18, 2025
@renovate renovate bot changed the title fix(deps): update minor dependencies fix(deps): update minor dependencies - autoclosed Mar 18, 2025
@renovate renovate bot closed this Mar 18, 2025
@renovate renovate bot deleted the renovate/minor-dependencies branch March 18, 2025 22:10
@renovate renovate bot changed the title fix(deps): update minor dependencies - autoclosed fix(deps): update minor dependencies Mar 20, 2025
@renovate renovate bot reopened this Mar 20, 2025
@renovate renovate bot force-pushed the renovate/minor-dependencies branch from 624f97e to 4ea04dc Compare March 20, 2025 15:11
@renovate renovate bot changed the title fix(deps): update minor dependencies fix(deps): update dependency @nuxt/content to v3.4.0 Mar 20, 2025
@renovate renovate bot force-pushed the renovate/minor-dependencies branch 2 times, most recently from d95b2c7 to 9458635 Compare March 21, 2025 21:34
@renovate renovate bot changed the title fix(deps): update dependency @nuxt/content to v3.4.0 fix(deps): update minor dependencies Mar 21, 2025
@renovate renovate bot changed the title fix(deps): update minor dependencies fix(deps): update minor dependencies - autoclosed Mar 22, 2025
@renovate renovate bot closed this Mar 22, 2025
@renovate renovate bot changed the title fix(deps): update minor dependencies - autoclosed fix(deps): update minor dependencies Mar 26, 2025
@renovate renovate bot reopened this Mar 26, 2025
@renovate renovate bot force-pushed the renovate/minor-dependencies branch from 248ed4d to 9458635 Compare March 26, 2025 13:07
@renovate renovate bot changed the title fix(deps): update minor dependencies chore(deps): update pnpm to v10.7.0 Mar 26, 2025
@renovate renovate bot force-pushed the renovate/minor-dependencies branch from 9458635 to f4b040c Compare March 26, 2025 19:01
@renovate renovate bot changed the title chore(deps): update pnpm to v10.7.0 fix(deps): update minor dependencies Mar 31, 2025
@renovate renovate bot force-pushed the renovate/minor-dependencies branch 2 times, most recently from e260273 to 76399d6 Compare April 7, 2025 19:03
@renovate renovate bot force-pushed the renovate/minor-dependencies branch 2 times, most recently from dc28528 to 1a013a8 Compare April 20, 2025 18:38
@renovate renovate bot force-pushed the renovate/minor-dependencies branch from 1a013a8 to cdeba82 Compare April 21, 2025 11:23
Copy link
Contributor Author

renovate bot commented Apr 21, 2025

⚠️ 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
 ERROR  Failed to switch pnpm to v10.6.1. Looks like pnpm CLI is missing at "/home/ubuntu/.local/share/pnpm/.tools/pnpm/10.6.1/bin" or is incorrect
spawnSync /home/ubuntu/.local/share/pnpm/.tools/pnpm/10.6.1/bin/pnpm ENOENT

@ClemCornet ClemCornet closed this Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant