Skip to content

chore(deps): update dependency @pinia/nuxt to v1 - #572

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/pinia-nuxt-1.x
Open

chore(deps): update dependency @pinia/nuxt to v1#572
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/pinia-nuxt-1.x

Conversation

@renovate

@renovate renovate Bot commented Jul 18, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@pinia/nuxt (source) ^0.11.3 → ^1.0.0 age confidence

Release Notes

vuejs/pinia (@​pinia/nuxt)

v1.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.0.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

Configuration

📅 Schedule: (UTC)

  • 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • 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 Jul 18, 2026
@renovate
renovate Bot force-pushed the renovate/pinia-nuxt-1.x branch from d9d5a8d to 1f59999 Compare July 19, 2026 00:36
@renovate
renovate Bot force-pushed the renovate/pinia-nuxt-1.x branch from 1f59999 to d4db295 Compare July 20, 2026 22:14
@renovate
renovate Bot force-pushed the renovate/pinia-nuxt-1.x branch from d4db295 to 464410b Compare July 21, 2026 05:30
@renovate
renovate Bot force-pushed the renovate/pinia-nuxt-1.x branch from 464410b to 4521a81 Compare July 25, 2026 23:28
@renovate
renovate Bot force-pushed the renovate/pinia-nuxt-1.x branch from 4521a81 to 938d451 Compare July 27, 2026 18:11
@renovate

renovate Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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
? Verifying lockfile against supply-chain policies (1146 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
.                                        | [WARN] deprecated conventional-changelog-cli@5.0.0
Progress: resolved 34, reused 0, downloaded 0, added 0
Progress: resolved 37, reused 0, downloaded 0, added 0
Progress: resolved 38, reused 0, downloaded 1, added 0
Progress: resolved 39, reused 0, downloaded 1, added 0
Progress: resolved 173, reused 0, downloaded 1, added 0
Progress: resolved 200, reused 0, downloaded 1, added 0
Progress: resolved 352, reused 0, downloaded 1, added 0
Progress: resolved 413, reused 0, downloaded 1, added 0
Progress: resolved 415, reused 0, downloaded 1, added 0
Progress: resolved 525, reused 0, downloaded 1, added 0
Progress: resolved 618, reused 0, downloaded 1, added 0
Progress: resolved 747, reused 0, downloaded 1, added 0
Progress: resolved 857, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (1146 entries in 18.2s)
Progress: resolved 1011, reused 0, downloaded 1, added 0
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 5 lockfile entries failed verification:
  @nuxt/kit@4.5.1 was published at 2026-07-27T10:17:41.837Z, within the minimumReleaseAge cutoff (2026-07-26T18:10:37.553Z)
  @nuxt/nitro-server@4.5.1 was published at 2026-07-27T10:17:45.980Z, within the minimumReleaseAge cutoff (2026-07-26T18:10:37.553Z)
  @nuxt/schema@4.5.1 was published at 2026-07-27T10:18:07.554Z, within the minimumReleaseAge cutoff (2026-07-26T18:10:37.553Z)
  @nuxt/vite-builder@4.5.1 was published at 2026-07-27T10:18:11.755Z, within the minimumReleaseAge cutoff (2026-07-26T18:10:37.553Z)
  nuxt@4.5.1 was published at 2026-07-27T10:17:58.963Z, within the minimumReleaseAge cutoff (2026-07-26T18:10:37.553Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

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

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants