Skip to content

chore(deps-dev): bump svelte-check from 4.3.5 to 4.4.6 in /prompt-launcher#33

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/prompt-launcher/svelte-check-4.4.6
Open

chore(deps-dev): bump svelte-check from 4.3.5 to 4.4.6 in /prompt-launcher#33
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/prompt-launcher/svelte-check-4.4.6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Apr 1, 2026

Copy link
Copy Markdown

Bumps svelte-check from 4.3.5 to 4.4.6.

Release notes

Sourced from svelte-check's releases.

svelte-check@4.4.6

Patch Changes

  • fix: prevent config loading message in svelte-check --incremental (#2974)

  • fix: resolve svelte files with NodeNext in --incremental/tsgo (#2990)

  • perf: various optimization with ast walk (#2969)

  • fix: prevent error with escape sequence in attribute (#2968)

  • fix: typescript 6.0 compatibility (#2988)

svelte-check@4.4.5

Patch Changes

  • fix: use Promise for async kit handler return types (#2966)

svelte-check@4.4.4

Patch Changes

  • fix: more robust detection of lang="ts" attribute (#2957)

  • fix: pass filename to warningFilter (#2959)

  • fix: resolve svelte files under path alias in --incremental/tsgo mode (#2955)

svelte-check@4.4.3

Patch Changes

  • fix: respect @ts-ignore etc comments within tags (#2950)

svelte-check@4.4.2

Patch Changes

  • fix: resolve shims correctly in --incremental/tsgo mode (cd1ff2f)

  • fix: include references in generated tsconfig.json in --incremental/tsgo mode (1990f74)

svelte-check@4.4.1

Patch Changes

  • fix: handle relative imports reaching outside working directory when using --incremental/--tsgo flags (#2942)

  • fix: support SvelteKit zero types in svelte-check --incremental (#2939)

svelte-check@4.4.0

Minor Changes

  • feat: provide --incremental and --tsgo flags (#2932)

... (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)

Bumps [svelte-check](https://github.com/sveltejs/language-tools) from 4.3.5 to 4.4.6.
- [Release notes](https://github.com/sveltejs/language-tools/releases)
- [Commits](https://github.com/sveltejs/language-tools/compare/svelte-check@4.3.5...svelte-check@4.4.6)

---
updated-dependencies:
- dependency-name: svelte-check
  dependency-version: 4.4.6
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Apr 1, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@ZeroPointSix ZeroPointSix left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

总体结论:本轮巡检审查了 PR #33 当前 head 2ac48df。该 PR 只升级 prompt-launchersvelte-check 小版本,前端 install/check/test/build 和 Linux Tauri 构建均通过;当前唯一失败的 Windows Tauri job 是下载 GitHub Action 时的 SSL 问题,未看到由本次依赖升级直接引入的阻塞代码风险。

关键发现:

  • 验证状态:GitHub Actions CI #42check-and-test (22.x) 完成成功,覆盖了依赖安装、Svelte/TypeScript check、单元测试和前端 build;build-tauri (ubuntu-latest) 也完成成功。
  • CI 失败边界:同一 run 的 build-tauri (windows-latest)Set up job 阶段失败,日志显示下载 dtolnay/rust-toolchain@stable zipball 时 SSL connection 建立失败,并在 3 次尝试后退出。这个失败发生在 checkout/build 之前,更像 runner/GitHub 网络临时问题;建议重跑该 job 或后续以新的 CI run 确认 Windows 包构建,而不是把它归因到 svelte-check 本身。
  • 兼容性:svelte-check4.3.54.4.6 属于同一主版本升级,release notes 中包含 TypeScript 6 兼容、NodeNext 增量解析和诊断优化。本 PR 本身仍保留 typescript ~5.6.2svelte ^5.0.0vite ^6.0.3,没有引入明显 peer dependency 冲突。
  • 中:package-lock.jsonsvelte-checkresolved 来源从 registry.npmmirror.com 变为 registry.npmjs.org。这通常是 Dependabot 生成环境差异,但会影响 lockfile 来源一致性。建议确认仓库是否要求固定 npm registry;如有要求,应按仓库配置重新生成 lockfile。

优先级建议:

  • 阻塞:无明确代码阻塞。
  • 中:重跑失败的 Windows Tauri job,确认不是持续性 runner/action 下载问题。
  • 中:确认 lockfile registry 来源变化是否符合仓库策略。

后续建议:

  • 如果 PR #31 的 TypeScript 6 升级后续推进,PR #33 反而是有价值的前置升级,因为 svelte-check@4.4.6 已包含 TypeScript 6 兼容修复;建议把两者的合并顺序和最终 CI 结果在对应 PR 中说明清楚。

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.

1 participant