Skip to content

chore(deps-dev): bump svelte from 5.55.5 to 5.55.7 in /frontend/web#128

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/web/svelte-5.55.7
Open

chore(deps-dev): bump svelte from 5.55.5 to 5.55.7 in /frontend/web#128
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/web/svelte-5.55.7

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 14, 2026

Bumps svelte from 5.55.5 to 5.55.7.

Release notes

Sourced from svelte's releases.

svelte@5.55.7

Patch Changes

svelte@5.55.6

Patch Changes

  • fix: leave stale promises to wait for a later resolution, instead of rejecting (#18180)

  • fix: keep dependencies of $state.eager/pending (#18218)

  • fix: reapply context after transforming error during SSR (#18099)

  • fix: don't rebase just-created batches (#18117)

  • chore: allow null for pending in typings (#18201)

  • fix: flush eager effects in production (#18107)

  • fix: rethrow error of failed iterable after calling return() (#18169)

  • fix: account for proxified instance when updating bind:this (#18147)

  • fix: ensure scheduled batch is flushed if not obsolete (#18131)

  • fix: resolve stale deriveds with latest value (#18167)

  • chore: remove unnecessary increment_pending calls (#18183)

  • fix: correctly compile component member expressions for SSR (#18192)

  • fix: reset source.updated stack traces after flush (#18196)

  • fix: replacing async 'blocking' strategy with 'merging' (#18205)

  • fix: allow @debug tags to reference awaited variables (#18138)

  • fix: re-run fallback props if dependencies update (#18146)

  • fix: abort running obsolete async branches (#18118)

... (truncated)

Changelog

Sourced from svelte's changelog.

5.55.7

Patch Changes

5.55.6

Patch Changes

  • fix: leave stale promises to wait for a later resolution, instead of rejecting (#18180)

  • fix: keep dependencies of $state.eager/pending (#18218)

  • fix: reapply context after transforming error during SSR (#18099)

  • fix: don't rebase just-created batches (#18117)

  • chore: allow null for pending in typings (#18201)

  • fix: flush eager effects in production (#18107)

  • fix: rethrow error of failed iterable after calling return() (#18169)

  • fix: account for proxified instance when updating bind:this (#18147)

  • fix: ensure scheduled batch is flushed if not obsolete (#18131)

  • fix: resolve stale deriveds with latest value (#18167)

  • chore: remove unnecessary increment_pending calls (#18183)

  • fix: correctly compile component member expressions for SSR (#18192)

  • fix: reset source.updated stack traces after flush (#18196)

  • fix: replacing async 'blocking' strategy with 'merging' (#18205)

  • fix: allow @debug tags to reference awaited variables (#18138)

  • fix: re-run fallback props if dependencies update (#18146)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [svelte](https://github.com/sveltejs/svelte/tree/HEAD/packages/svelte) from 5.55.5 to 5.55.7.
- [Release notes](https://github.com/sveltejs/svelte/releases)
- [Changelog](https://github.com/sveltejs/svelte/blob/main/packages/svelte/CHANGELOG.md)
- [Commits](https://github.com/sveltejs/svelte/commits/svelte@5.55.7/packages/svelte)

---
updated-dependencies:
- dependency-name: svelte
  dependency-version: 5.55.7
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests updating dependencies javascript Pull requests that update javascript code labels May 14, 2026
@dependabot dependabot Bot requested a review from KooshaPari as a code owner May 14, 2026 21:57
@dependabot dependabot Bot added dependencies Pull requests updating dependencies javascript Pull requests that update javascript code labels May 14, 2026
@codeant-ai
Copy link
Copy Markdown

codeant-ai Bot commented May 14, 2026

Skipping PR review because a bot author is detected.

If you want to trigger CodeAnt AI, comment @codeant-ai review to trigger a manual review.

@sonarqubecloud
Copy link
Copy Markdown

@socket-security
Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​svelte@​5.55.7881008898100

View full report

Copy link
Copy Markdown

@kilo-code-bot kilo-code-bot Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review Summary

Status: 2 Issues Found | Recommendation: Request Changes

Overview

Severity Count
CRITICAL 1
WARNING 1
Issue Details (click to expand)

CRITICAL

File Line Issue
frontend/web/package.json 58 svelte 5.55.7 requires devalue ^5.8.1, but overrides/resolutions pin devalue to 5.7.1 (incompatible)

WARNING

File Line Issue
frontend/web/yarn.lock 1784 devalue 5.7.1 resolves to ^5.8.1 range — semver violation caused by override
Other Observations (not in diff)

The overrides and resolutions sections in package.json both pin devalue to 5.7.1. Svelte 5.55.7's package.json declares devalue: ^5.8.1. With Yarn 1.22.21, this forced downgrade will cause installation to fail with a version conflict error, as 5.7.1 is outside the ^5.8.1 range.

Required fix: Either remove the devalue override entirely or update both overrides and resolutions to devalue: "5.8.1" (or "^5.8.1"). The lockfile also needs regeneration after fixing package.json.

Files Reviewed (2 files)
  • frontend/web/package.json - 1 CRITICAL
  • frontend/web/yarn.lock - 1 WARNING (symptom of root cause)

Comment thread frontend/web/package.json
"storybook": "^10.3.5",
"svelte": "^5.53.5",
"svelte": "^5.55.7",
"svelte-check": "^4.4.6",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CRITICAL: Version conflict: svelte 5.55.7 requires devalue ^5.8.1, but overrides.devalue: "5.7.1" and resolutions.devalue: "5.7.1" forcibly downgrade it. This creates an unsolvable dependency constraint — Yarn 1 will fail to install because 5.7.1 is not within ^5.8.1. Fix: update or remove the devalue override before merging.

Suggested change
"svelte-check": "^4.4.6",
"overrides": {
/* ... other overrides ... */
"devalue": "5.8.1",
/* ... */
},
"resolutions": {
/* ... other resolutions ... */
"devalue": "5.8.1",
/* ... */
},

Comment thread frontend/web/yarn.lock
integrity sha512-Btj2BOOO83o3WyH59e8MgXsxEQVcarkUOpEYrubB0urwnN10yQ364rsiByU11nZlqWYZm05i/of7io4mzihBtQ==

devalue@5.7.1, devalue@^5.6.4:
devalue@5.7.1, devalue@^5.6.4, devalue@^5.8.1:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: This lockfile entry shows devalue@5.7.1 resolving to the ^5.8.1 range — a semver violation. This is a symptom of the package.json override forcing an incompatible version. The lockfile must be regenerated after fixing the override.

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

Labels

dependencies Pull requests updating dependencies javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants