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

fix(deps): update dependency pinia to v2.2.8 #824

Merged
merged 1 commit into from
Nov 29, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 29, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pinia 2.2.7 -> 2.2.8 age adoption passing confidence
pinia 2.1.7 -> 2.2.8 age adoption passing confidence

Release Notes

vuejs/pinia (pinia)

v2.2.8

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 these updates 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 enabled auto-merge (squash) November 29, 2024 08:49
Copy link
Contributor Author

renovate bot commented Nov 29, 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: examples/nuxt-3-universal-example/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: nuxt-3-universal-example@undefined
npm ERR! Found: vue@3.4.29
npm ERR! node_modules/vue
npm ERR!   peer vue@"^3.3.4" from @nuxt/vite-builder@3.12.2
npm ERR!   node_modules/@nuxt/vite-builder
npm ERR!     @nuxt/vite-builder@"3.12.2" from nuxt@3.12.2
npm ERR!     node_modules/nuxt
npm ERR!       peer nuxt@"^3.9.0" from @nuxt/devtools@1.3.3
npm ERR!       node_modules/@nuxt/devtools
npm ERR!         @nuxt/devtools@"^1.3.3" from nuxt@3.12.2
npm ERR!       2 more (@nuxt/devtools-kit, the root project)
npm ERR!   peer vue@">=2.7 || >=3" from @unhead/vue@1.9.13
npm ERR!   node_modules/@unhead/vue
npm ERR!     @unhead/vue@"^1.9.13" from nuxt@3.12.2
npm ERR!     node_modules/nuxt
npm ERR!       peer nuxt@"^3.9.0" from @nuxt/devtools@1.3.3
npm ERR!       node_modules/@nuxt/devtools
npm ERR!         @nuxt/devtools@"^1.3.3" from nuxt@3.12.2
npm ERR!       2 more (@nuxt/devtools-kit, the root project)
npm ERR!   17 more (@vitejs/plugin-vue, @vitejs/plugin-vue-jsx, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! pinia@"2.2.8" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: vue@2.6.14
npm ERR! node_modules/vue
npm ERR!   peer vue@"^2.6.14 || ^3.5.11" from pinia@2.2.8
npm ERR!   node_modules/pinia
npm ERR!     pinia@"2.2.8" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-29T11_16_40_329Z-debug-0.log

@renovate renovate bot force-pushed the renovate/pinia-2.x-lockfile branch from 0743e13 to c29c5ae Compare November 29, 2024 11:16
@renovate renovate bot merged commit 243e082 into main Nov 29, 2024
15 of 16 checks passed
@renovate renovate bot deleted the renovate/pinia-2.x-lockfile branch November 29, 2024 11:19
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