Skip to content

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

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

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

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 5, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
@types/youtube (source) ^0.1.0^0.1.2 age confidence peerDependencies patch
@unhead/vue (source) ^2.0.3^2.1.10 age confidence peerDependencies minor
actions/checkout v6.0.1v6.0.2 age confidence action patch
actions/stale v10.0.0v10.2.0 age confidence action minor
posthog-js (source) ^1.0.0^1.358.0 age confidence peerDependencies minor

Release Notes

unjs/unhead (@​unhead/vue)

v2.1.10

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.9

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.1

Compare Source

No significant changes

    View changes on GitHub

v2.1.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.0.19

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.18

Compare Source

   🏎 Performance
    View changes on GitHub

v2.0.17

Compare Source

No significant changes

    View changes on GitHub

v2.0.14

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.13

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.12

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.11

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.10

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.9

Compare Source

   🏎 Performance
    View changes on GitHub

v2.0.8

Compare Source

No significant changes

    View changes on GitHub

v2.0.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
actions/checkout (actions/checkout)

v6.0.2

Compare Source

actions/stale (actions/stale)

v10.2.0

Compare Source

v10.1.1

Compare Source

What's Changed

Bug Fix
Improvement
Dependency Upgrades

New Contributors

Full Changelog: actions/stale@v10...v10.1.1

v10.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/stale@v10...v10.1.0

PostHog/posthog-js (posthog-js)

v1.358.0

Compare Source

1.358.0

Minor Changes
Patch Changes

v1.357.2

Compare Source

1.357.2

Patch Changes

v1.357.1

Compare Source

1.357.1

Patch Changes

v1.357.0

Compare Source

1.357.0

Minor Changes
Patch Changes
  • #​3179 0dce119 Thanks @​TueHaulund! - Bump @​posthog/rrweb-* to 0.0.45 — reuses a single OffscreenCanvas in the canvas recording worker instead of allocating a new one per frame, fixing a memory leak in Safari where GPU-backed canvas resources were not being garbage collected promptly
    (2026-03-02)
  • Updated dependencies [4f885c0]:

v1.356.2

Compare Source

1.356.2

Patch Changes
  • #​3174 e9127d8 Thanks @​TueHaulund! - Detect and report when rrweb fails to initialize. rrweb's record() silently swallows startup errors and returns undefined, which previously left the SDK reporting an active recording status while capturing zero data. The SDK now checks the return value and reports a new rrweb_error status, making the failure visible in debug properties.
    (2026-03-02)

  • #​3175 6ee5f12 Thanks @​TueHaulund! - Fix memory leak in canvas recording on Safari < 16.4 where ImageBitmaps were never closed when OffscreenCanvas was unavailable in the web worker.
    (2026-03-02)

  • #​3178 186871a Thanks @​TueHaulund! - Skip canvas FPS recording entirely on browsers without OffscreenCanvas support (Safari < 16.4) instead of running a wasteful requestAnimationFrame loop that can never produce data. Also includes displayWidth/displayHeight in canvas mutation data for correct replay sizing.
    (2026-03-02)

  • #​3176 87bae20 Thanks @​dustinbyrne! - fix: Drop explicit exports
    (2026-03-02)

  • #​3172 2e46959 Thanks @​dustinbyrne! - fix: Compressed requests use ArrayBuffer
    (2026-03-02)

  • Updated dependencies []:

v1.356.1

Compare Source

1.356.1

Patch Changes
  • #​3128 a500d14 Thanks @​ksvat! - wait for fresh config before recording start decision, add new recorder status, output recording started event
    (2026-02-27)
  • Updated dependencies []:

v1.356.0

Compare Source

1.356.0

Minor Changes
Patch Changes
  • #​3154 a47179c Thanks @​slshults! - fix: Improve tablet device type detection when Chrome sends desktop-like UA strings

    Chrome on Android tablets defaults to "request desktop site" mode, sending a UA string
    indistinguishable from desktop Linux. This uses the Client Hints API (navigator.userAgentData.platform)
    and touch capability (navigator.maxTouchPoints) to correctly classify these devices as Tablet or Mobile
    when UA-based detection falls through to the Desktop default. (2026-02-26)

  • #​3145 d741668 Thanks @​dmarticus! - Adds a remote_config_refresh_interval_ms config option to control how often feature flags are automatically refreshed in long-running sessions.
    (2026-02-26)

  • Updated dependencies [ec54fd8, d741668]:

v1.355.0

Compare Source

1.355.0

Minor Changes
Patch Changes

v1.354.4

Compare Source

1.354.4

Patch Changes

v1.354.3

Compare Source

1.354.3

Patch Changes

v1.354.2

Compare Source

1.354.2

Patch Changes

v1.354.1

Compare Source

1.354.1

Patch Changes

v1.354.0

Compare Source

1.354.0

Minor Changes
Patch Changes

v1.353.1

Compare Source

1.353.1

Patch Changes

v1.353.0

Compare Source

1.353.0

Minor Changes
Patch Changes

v1.352.1

Compare Source

1.352.1

Patch Changes

v1.352.0

Compare Source

1.352.0

Minor Changes
Patch Changes

v1.351.4

Compare Source

1.351.4
Patch Changes
  • #​3119 2649a9a Thanks @​dmarticus! - Adds a fresh option to getFeatureFlag(), getFeatureFlagResult(), and isFeatureEnabled() that only returns values loaded from the server, not cached localStorage values.
    (2026-02-19)
  • Updated dependencies [2649a9a]:

v1.351.3

Compare Source

1.351.3
Patch Changes

v1.351.2

Compare Source

1.351.2
Patch Changes

v1.351.1

Compare Source

1.351.1
Patch Changes

v1.351.0

Compare Source

1.351.0
Minor Changes
Patch Changes

v1.350.0

Compare Source

1.350.0
Minor Changes
  • #​2895 1b47203 Thanks @​benjackwhite! - RemoteConfig (config.js) has been loaded for ages and is in use by us in production. This PR makes it the sole config loading mechanism for posthog-js, removing the legacy /flags/?v=2&config=true path and the __preview_remote_config gate.
    (2026-02-17)
Patch Changes

v1.349.0

Compare Source

1.349.0
Minor Changes
Patch Changes

v1.348.0

Compare Source

1.348.0
Minor Changes
Patch Changes

v1.347.2

Compare Source

1.347.2

Patch Changes

v1.347.1

Compare Source

1.347.1

Patch Changes

v1.347.0

Compare Source

1.347.0

Minor Changes
Patch Changes

v1.346.0

Compare Source

1.346.0

Minor Changes
Patch Changes

v1.345.5

Compare Source

1.345.5

Patch Changes
  • #​3060 7437982 Thanks @​pauldambra! - Add missing featureFlags property and OverrideFeatureFlagsOptions type to PostHog interface, restore set_config to the loaded callback type, and add featureFlagsReloading to on() event types
    (2026-02-11)
  • Updated dependencies [7437982]:

v1.345.4

Compare Source

1.345.4

Patch Changes

v1.345.3

Compare Source

1.345.3

Patch Changes

v1.345.2

Compare Source

1.345.2

Patch Changes

v1.345.1

Compare Source

1.345.1

Patch Changes

v1.345.0

Compare Source

1.345.0

Minor Changes
Patch Changes

v1.344.0

Compare Source

v1.343.2

Compare Source

1.343.2

Patch Changes

v1.343.1

Compare Source

1.343.1

Patch Changes

v1.343.0

Compare Source

1.343.0

Minor Changes
Patch Changes

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.

@vercel
Copy link
Contributor

vercel bot commented Apr 5, 2025

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

Project Deployment Actions Updated (UTC)
scripts-docs Error Error Mar 4, 2026 1:32pm
scripts-playground Error Error Mar 4, 2026 1:32pm

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9c4e39b to 5bfebea Compare April 5, 2025 00:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5bfebea to 7804f68 Compare April 6, 2025 09:08
@renovate renovate bot changed the title chore(deps): update resolutions typescript to v5.8.3 chore(deps): update all non-major dependencies Apr 6, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7804f68 to 2d975ff Compare April 7, 2025 04:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2d975ff to 0104ff1 Compare April 7, 2025 08:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0104ff1 to 8120e32 Compare April 7, 2025 15:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8120e32 to 5ec9f5e Compare April 7, 2025 18:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5ec9f5e to efcb3b7 Compare April 8, 2025 08:39
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from efcb3b7 to 1a61aec Compare April 10, 2025 00:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1a61aec to cf8e7f8 Compare April 10, 2025 09:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cf8e7f8 to 2b13cf8 Compare April 11, 2025 01:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 64d7d5a to 6132302 Compare April 16, 2025 07:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6132302 to 360e116 Compare April 16, 2025 14:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 360e116 to aa97a8b Compare April 17, 2025 00:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from aa97a8b to 714cf9d Compare April 17, 2025 08:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 714cf9d to bdbb60c Compare April 17, 2025 18:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from bdbb60c to 9343bf3 Compare April 18, 2025 20:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9343bf3 to fb7fea7 Compare April 21, 2025 12:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fb7fea7 to 556aaae Compare April 21, 2025 16:40
@pkg-pr-new
Copy link

pkg-pr-new bot commented Jul 16, 2025

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/scripts@446

commit: c3f46fd

"@nuxt/image": "^1.11.0",
"@nuxt/scripts": "workspace:*",
"@nuxt/ui": "4.0.0",
"@nuxt/ui": "4.2.1",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"@nuxt/ui": "4.2.1",
"@nuxt/ui": "^4.2.1",

The @nuxt/ui dependency is pinned to 4.2.1 without a caret, which is inconsistent with all other dependencies in this file that use flexible versioning with the ^ prefix.

View Details

Analysis

Inconsistent version pinning for @nuxt/ui dependency

What fails: docs/package.json line 20 specifies @nuxt/ui as pinned version 4.2.1 (without caret prefix), while all 13 other dependencies use caret versioning (^) for flexible version constraints within the major version.

How to reproduce:

cat docs/package.json | grep -A 15 '"dependencies"'

Result: Shows "@nuxt/ui": "4.2.1" (pinned) while all surrounding dependencies have caret prefix:

  • "@nuxt/content": "^3.8.2"
  • "@nuxt/fonts": "^0.12.1"
  • "@nuxthq/studio": "^2.2.1"
  • All other 10 dependencies also use ^ prefix

Expected behavior: According to npm semantic versioning, caret versioning allows compatible updates (minor/patch versions) within a major version. The project consistently uses this pattern for all other dependencies, so @nuxt/ui should be ^4.2.1 to match the established convention and allow patch/minor updates like other dependencies.

Root cause: Automated dependency update (Renovate bot commit 0b37709) preserved the previous pinned format when bumping the version from 4.0.0 to 4.2.1, rather than applying the project's standard caret versioning pattern used throughout the file.

package.json Outdated
"posthog-js": "^1.0.0"
"@types/youtube": "^0.1.2",
"@unhead/vue": "^2.1.2",
"posthog-js": "^1.321.2"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"posthog-js": "^1.321.2"
"posthog-js": "^1.0.0"

The posthog-js peer dependency constraint changed from ^1.0.0 to ^1.321.2, which is unusually restrictive and appears unintentional given the patch version bump in devDependencies (1.321.1 → 1.321.2).

View Details

Analysis

Overly restrictive posthog-js peer dependency breaks backward compatibility

What fails: The posthog-js peer dependency constraint in package.json was changed from ^1.0.0 to ^1.321.2 (commit 1536ad2), restricting supported versions to 1.321.2+ and rejecting all prior versions (1.0.0-1.321.1) that would previously install.

How to reproduce:

# User has posthog-js 1.200.0 installed (legitimate version under old ^1.0.0 constraint)
npm install @nuxt/scripts
# After update, npm now rejects this version because 1.200.0 does not satisfy ^1.321.2

Result: npm/pnpm install fails with: "posthog-js@1.200.0 not satisfied by ^1.321.2"

Expected: The peer dependency should remain at ^1.0.0 (or similar permissive constraint) since:

  • Code only uses posthog.init() and basic config options (api_host, capture_pageview, disable_session_recording) available since 1.0.0
  • The devDependency update was only a patch bump (1.222.0 → 1.321.2), not a major version requiring API changes
  • Peer dependencies should be permissive to maximize compatibility
  • Semantic versioning guidance indicates patch/minor version updates within the same major version should be backward compatible

This change appears to be an error from automated dependency update tooling (Renovate) that applied the same pinpoint version to both devDependencies and peerDependencies.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 4, 2026

⚠️ 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
Scope: all 3 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 33, reused 0, downloaded 0, added 0
Progress: resolved 48, reused 0, downloaded 0, added 0
Progress: resolved 51, reused 0, downloaded 0, added 0
Progress: resolved 111, reused 0, downloaded 0, added 0
Progress: resolved 166, reused 0, downloaded 0, added 0
Progress: resolved 196, reused 0, downloaded 0, added 0
Progress: resolved 269, reused 0, downloaded 0, added 0
Progress: resolved 309, reused 0, downloaded 0, added 0
Progress: resolved 361, reused 0, downloaded 0, added 0
Progress: resolved 413, reused 0, downloaded 0, added 0
Progress: resolved 465, reused 0, downloaded 0, added 0
Progress: resolved 497, reused 0, downloaded 0, added 0
Progress: resolved 523, reused 0, downloaded 0, added 0
Progress: resolved 559, reused 0, downloaded 0, added 0
Progress: resolved 643, reused 0, downloaded 0, added 0
Progress: resolved 659, reused 0, downloaded 0, added 0
Progress: resolved 679, reused 0, downloaded 0, added 0
Progress: resolved 734, reused 0, downloaded 0, added 0
Progress: resolved 790, reused 0, downloaded 0, added 0
Progress: resolved 803, reused 0, downloaded 0, added 0
 WARN  Request took 18780ms: https://registry.npmjs.org/vite
Progress: resolved 854, reused 0, downloaded 0, added 0
Progress: resolved 902, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/nuxt/scripts/client:
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "chokidar@4.0.3" (possible package takeover)

This error happened while installing the dependencies of nuxt@4.3.1
 at @nuxt/vite-builder@4.3.1
 at vite-plugin-checker@0.12.0

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had provenance attestation, but this version has no trust evidence. A trust downgrade may indicate a supply chain incident.

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