Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 18, 2025

This PR contains the following updates:

Package Change Age Confidence
@pinia/testing (source) ^0.1.7 -> ^1.0.2 age confidence

Release Notes

vuejs/pinia (@​pinia/testing)

v1.0.2

Compare Source

v1.0.1

Compare Source

v1.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "before 5am on wednesday" in timezone Europe/Vienna, 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.

Copy link
Contributor Author

renovate bot commented Jun 18, 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: package-lock.json
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   pinia@"^2.3.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer pinia@">=3.0.3" from @pinia/[email protected]
npm error node_modules/@pinia/testing
npm error   @pinia/testing@"^1.0.2" 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 /runner/cache/others/npm/_logs/2025-08-13T13_39_19_746Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-08-13T13_39_19_746Z-debug-0.log

@renovate renovate bot requested review from GretaD and kesselb as code owners June 18, 2025 00:58
@renovate renovate bot force-pushed the renovate/main-pinia-testing-1.x branch 2 times, most recently from 1131d9d to 336607a Compare August 10, 2025 12:27
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/main-pinia-testing-1.x branch from 336607a to b02a650 Compare August 13, 2025 13:39
@ChristophWurst
Copy link
Member

npm error peer pinia@">=3.0.3" from @pinia/[email protected]

but

Pinia v3 is a boring major release with no new features. It drops deprecated APIs and updates major dependencies. It only supports Vue 3. If you are using Vue 2, you can keep using v2. If you need help, book help with Pinia's author.

so this is blocked as long as we are on Vue 2

@ChristophWurst ChristophWurst deleted the renovate/main-pinia-testing-1.x branch August 13, 2025 15:26
Copy link
Contributor Author

renovate bot commented Aug 13, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 1.x releases. But if you manually upgrade to 1.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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

Successfully merging this pull request may close these issues.

1 participant