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

chore(deps): update dependency svelte-check to ^4.0.6 #456

Merged
merged 1 commit into from
Nov 9, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 9, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
svelte-check ^4.0.5 -> ^4.0.6 age adoption passing confidence

Release Notes

sveltejs/language-tools (svelte-check)

v4.0.6

Compare Source

  • chore: autotype const load = ... declarations (#​2540)
  • chore: provide component instance type in Svelte 5 (#​2553)
  • chore: support typescript 5.6 (#​2545)
  • fix: infer object and array shapes from fallback types (#​2562)

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 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 enabled auto-merge (squash) November 9, 2024 02:27
Copy link
Contributor Author

renovate bot commented Nov 9, 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: frontend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/svelte
npm error   dev svelte@"^5.1.12" from the root project
npm error   peer svelte@"^4.0.0 || ^5.0.0-next.0" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/kit
npm error     dev @sveltejs/kit@"^2.8.0" from the root project
npm error     peer @sveltejs/kit@"^2.0.0" from @sveltejs/[email protected]
npm error     node_modules/@sveltejs/adapter-auto
npm error       dev @sveltejs/adapter-auto@"^3.3.1" from the root project
npm error   4 more (@sveltejs/vite-plugin-svelte, ...)
npm error
npm error Could not resolve dependency:
npm error peer svelte@"^3.2.0" from [email protected]
npm error node_modules/eslint-plugin-svelte3
npm error   dev eslint-plugin-svelte3@"^4.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/svelte
npm error   peer svelte@"^3.2.0" from [email protected]
npm error   node_modules/eslint-plugin-svelte3
npm error     dev eslint-plugin-svelte3@"^4.0.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-11-09T02_27_42_344Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-09T02_27_42_344Z-debug-0.log

@renovate renovate bot merged commit 2da464a into main Nov 9, 2024
5 of 6 checks passed
@renovate renovate bot deleted the renovate/svelte-check-4.x branch November 9, 2024 02:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants