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 @iconify/svelte to 4.1.0 #172

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

Conversation

chii-bot[bot]
Copy link
Contributor

@chii-bot chii-bot bot commented Apr 28, 2024

This PR contains the following updates:

Package Type Update Change
@iconify/svelte (source) devDependencies major 3.1.0 -> 4.1.0

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 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 has been generated by Renovate Bot.

@chii-bot chii-bot bot requested a review from toboshii as a code owner April 28, 2024 18:23
@chii-bot chii-bot bot added the type/major label Apr 28, 2024
@chii-bot
Copy link
Contributor Author

chii-bot bot commented Apr 28, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: hajimari@0.3.0
npm ERR! Found: svelte@3.50.1
npm ERR! node_modules/svelte
npm ERR!   dev svelte@"3.50.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer svelte@">4.0.0" from @iconify/svelte@4.0.2
npm ERR! node_modules/@iconify/svelte
npm ERR!   dev @iconify/svelte@"4.0.2" 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-05-04T14_18_39_453Z-debug-0.log

@chii-bot chii-bot bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 28, 2024
@chii-bot chii-bot bot changed the title chore(deps): update @iconify/svelte to 4.0.0 chore(deps): update @iconify/svelte to 4.0.1 Apr 29, 2024
@chii-bot chii-bot bot force-pushed the renovate/iconify-svelte-4.x branch 2 times, most recently from 853769b to 098c2fa Compare May 4, 2024 14:18
@chii-bot chii-bot bot changed the title chore(deps): update @iconify/svelte to 4.0.1 chore(deps): update @iconify/svelte to 4.0.2 May 4, 2024
| datasource | package         | from  | to    |
| ---------- | --------------- | ----- | ----- |
| npm        | @iconify/svelte | 3.1.0 | 4.1.0 |
@chii-bot chii-bot bot changed the title chore(deps): update @iconify/svelte to 4.0.2 chore(deps): update @iconify/svelte to 4.1.0 Dec 7, 2024
@chii-bot
Copy link
Contributor Author

chii-bot bot commented Dec 7, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: hajimari@0.3.0
npm ERR! Found: svelte@3.50.1
npm ERR! node_modules/svelte
npm ERR!   dev svelte@"3.50.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer svelte@">4.0.0" from @iconify/svelte@4.1.0
npm ERR! node_modules/@iconify/svelte
npm ERR!   dev @iconify/svelte@"4.1.0" 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-12-07T07_24_01_964Z-debug-0.log

@chii-bot chii-bot bot force-pushed the renovate/iconify-svelte-4.x branch from 098c2fa to c7c5776 Compare December 7, 2024 07:24
@chii-bot chii-bot bot changed the title chore(deps): update @iconify/svelte to 4.1.0 chore(deps): update @iconify/svelte to 4.1.0 - autoclosed Dec 8, 2024
@chii-bot chii-bot bot closed this Dec 8, 2024
@chii-bot chii-bot bot deleted the renovate/iconify-svelte-4.x branch December 8, 2024 18:31
@chii-bot chii-bot bot changed the title chore(deps): update @iconify/svelte to 4.1.0 - autoclosed chore(deps): update @iconify/svelte to 4.1.0 Dec 9, 2024
@chii-bot chii-bot bot reopened this Dec 9, 2024
@chii-bot chii-bot bot restored the renovate/iconify-svelte-4.x branch December 9, 2024 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/major
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants