Skip to content
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

Update dependency @pinia/nuxt to v0.9.0 #291

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@pinia/nuxt (source) 0.4.11 -> 0.9.0 age adoption passing confidence

Release Notes

vuejs/pinia (@​pinia/nuxt)

v0.9.0

Compare Source

v0.8.0

Compare Source

v0.7.0

Compare Source

v0.6.1

Compare Source

v0.6.0

Compare Source

v0.5.5

Compare Source

v0.5.4

Compare Source

Please refer to CHANGELOG.md for details.

v0.5.3

Compare Source

Please refer to CHANGELOG.md for details.

v0.5.2

Compare Source

Please refer to CHANGELOG.md for details.

v0.5.1

Compare Source

Please refer to CHANGELOG.md for details.

v0.5.0

Compare Source

Please refer to CHANGELOG.md for details.


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 is behind base branch, 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 renovate Created by Renovate label Dec 25, 2024
Copy link
Contributor Author

renovate bot commented Dec 25, 2024

⚠️ 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: package-lock.json
npm warn cli npm v11.0.0 does not support Node.js v20.12.2. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/pinia
npm error   dev pinia@"2.0.36" from the root project
npm error
npm error Could not resolve dependency:
npm error peer pinia@"^2.3.0" from @pinia/[email protected]
npm error node_modules/@pinia/nuxt
npm error   dev @pinia/nuxt@"0.9.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-25T08_08_34_141Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-25T08_08_34_141Z-debug-0.log

@renovate renovate bot force-pushed the renovate/pinia-nuxt-0.x branch from aaaf7a3 to ac018d1 Compare December 25, 2024 08:08
Copy link

netlify bot commented Dec 25, 2024

Deploy Preview for anohi-no-tweet failed.

Name Link
🔨 Latest commit ac018d1
🔍 Latest deploy log https://app.netlify.com/sites/anohi-no-tweet/deploys/676bbd898a0d4f0008cc7b0e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
renovate Created by Renovate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants