[balena-renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	^5.9.3 → ^6.0.0

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.3: TypeScript 6.0.3

Compare Source

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).
• fixed issues query for TypeScript 6.0.3 (Stable).

Downloads are available on:

• npm

v6.0.2: TypeScript 6.0

Compare Source

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).

Downloads are available on:

• npm

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 has been generated by Mend Renovate CLI.

[balena-renovate]

⚠️ 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 warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: ts-jest@29.4.6
npm error Found: typescript@6.0.3
npm error node_modules/typescript
npm error   dev typescript@"^6.0.0" from the root project
npm error   peerOptional typescript@">= 4.9.x" from @storybook/react@10.5.8
npm error   node_modules/@storybook/react
npm error     @storybook/react@"10.5.8" from @storybook/react-webpack5@10.5.8
npm error     node_modules/@storybook/react-webpack5
npm error       dev @storybook/react-webpack5@"^10.5.8" from the root project
npm error   15 more (@storybook/react-docgen-typescript-plugin, ...)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.3 <6" from ts-jest@29.4.6
npm error node_modules/ts-jest
npm error   dev ts-jest@"^29.4.6" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@">=4.3 <6" from ts-jest@29.4.6
npm error   node_modules/ts-jest
npm error     dev ts-jest@"^29.4.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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/2026-10-29T18_01_54_188Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-10-29T18_01_54_188Z-debug-0.log

[flowzone-app]

Website deployed to CF Pages, 👀 preview link https://fb24a12c.balena-design-system.pages.dev

[balena-renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[thgreasi]

Since rootDir is just src, do we actually need this?
I also just saw that we are only linting src...

[myarmolinsky]

I checked with claude:

Yes, you need it, though rootDir isn't the reason. The two settings do different jobs:

- rootDir: "src" only sets how output paths are laid out under dist/. It doesn't decide which files get compiled; "include": ["src"] does.
- types sets which global @types/* packages get loaded. TypeScript 6 changed the default from "every package under node_modules/@types" to [], so @types/jest is no longer picked up automatically. 

[thgreasi]

Draft--proving since I think it's worth a try to create a separate tsconfig.dist.json, which wouldn't have jest types at all. (check how we do it in other repos)