build(deps): bump jotai from 2.20.3 to 3.0.0 in /front

[dependabot]

Bumps jotai from 2.20.3 to 3.0.0.

Release notes

Sourced from jotai's releases.

v3.0.0

👻 Jotai v3 is here! 🎉

This is a mostly backward-compatible update, dropping some legacy support and deprecated APIs.

Migration Guide

https://github.com/pmndrs/jotai/blob/main/docs/guides/migrating-to-v3.mdx

What's Changed

• v3 by @​dai-shi in pmndrs/jotai#3337
• chore(deps): update dev dependencies (breaking for v3: drop node 20) by @​dai-shi in pmndrs/jotai#3367

Full Changelog: pmndrs/jotai@v2.20.3...v3.0.0

v3.0.0-alpha.1

Includes v2.20.3 changes.

What's Changed

• fix(unwrap): prevent infinite microtask loop on rejected source recompute by @​dai-shi with @​Copilot in pmndrs/jotai#3363

New Contributors

• @​dai-shi with @​Copilot made their first contribution in pmndrs/jotai#3363

Full Changelog: pmndrs/jotai@v3.0.0-alpha.0...v3.0.0-alpha.1

v3.0.0-alpha.0

https://github.com/pmndrs/jotai/blob/v3/docs/guides/migrating-to-v3.mdx

What's Changed

• [v3] drop old TS by @​dai-shi in pmndrs/jotai#3336
• [v3] drop UMD and SystemJS builds by @​dai-shi in pmndrs/jotai#3338
• [v3] drop old node by @​dai-shi in pmndrs/jotai#3339
• [v3] module-first package by @​dai-shi in pmndrs/jotai#3340
• [v3] drop CJS by @​dai-shi in pmndrs/jotai#3341
• [v3] use NODE_ENV directly by @​dai-shi in pmndrs/jotai#3342
• [v3] drop rollup by @​dai-shi in pmndrs/jotai#3344
• [v3] drop old React by @​dai-shi in pmndrs/jotai#3345
• [v3] es2020 target by @​dai-shi in pmndrs/jotai#3346
• [v3] drop atomFamily by @​dai-shi in pmndrs/jotai#3347
• [v3] drop loadable by @​dai-shi in pmndrs/jotai#3348
• [v3] drop jotai/babel by @​dai-shi in pmndrs/jotai#3349
• [v3] drop setSelf by @​dai-shi in pmndrs/jotai#3350
• [v3] useAtomValueRaw & useAtomValueRawSync by @​dai-shi in pmndrs/jotai#3351
• [v3] redesign buildingBlocks by @​dai-shi in pmndrs/jotai#3358
• [v3] migration guide by @​dai-shi in pmndrs/jotai#3359

Full Changelog: pmndrs/jotai@v2.20.2...v3.0.0-alpha.0

Commits

• 89d4fdd v3.0.0
• a52e426 chore(deps): update dev dependencies (breaking for v3: drop node 20) (#3367)
• 0adc6c6 v3 (#3337)
• 8d5724b Clarify that effects run after the triggering write completes. (#3365)
• See full diff in compare view

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.21%. Comparing base (d7fdcd3) to head (82a3130).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2904   +/-   ##
=======================================
  Coverage   74.21%   74.21%           
=======================================
  Files         330      330           
  Lines       25393    25393           
  Branches     2534     2533    -1     
=======================================
  Hits        18845    18845           
  Misses       6498     6498           
  Partials       50       50           

Flag	Coverage Δ
backend	99.64% <ø> (ø)
frontend	66.85% <ø> (ø)
sharedComponents	44.29% <ø> (ø)
sharedFront	91.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pylipp]

@copilot consider https://github.com/pmndrs/jotai/blob/main/docs/guides/migrating-to-v3.mdx and tell me if the upgrade is compatible with the current code. E.g. which parts using jotai are affected and need to be changed? Is my stack and my dev environment compatible with the upgrade?

[Copilot]

@copilot consider https://github.com/pmndrs/jotai/blob/main/docs/guides/migrating-to-v3.mdx and tell me if the upgrade is compatible with the current code. E.g. which parts usin...

Reviewed the v3 migration guide. Summary:

Public API unchanged — useAtom, useAtomValue, useSetAtom keep the same signatures/behavior. Only one subtle mount-timing change is mentioned for useAtomValue, which is unlikely to affect our usage patterns.

Affected/removed features — checked our codebase for each:

• atomFamily (moved to jotai-family) — not used anywhere in front/src.
• loadable util (removed, replace with unwrap) — not used; we don't import it.
• jotai/babel plugins (moved to jotai-babel) — not configured in our babel/vite setup.
• setSelf option in read function — not used.
• delay option in useAtom/useAtomValue — not used.
• We only use atomWithStorage and useHydrateAtoms from jotai/utils (front/src/stores/globalCacheStore.ts, front/src/tests/test-utils.tsx), both of which are still supported entry points in v3.

So the code itself is compatible — no source changes needed.

Requirement/environment changes to be aware of:

• React ≥18 (we're on 18.3.1 ✅), TypeScript ≥5.5 (we're on 5.9.3 ✅).
• Node.js ≥22.12.0 is now required per jotai's package.json engines field — our CI/CircleCI images and copilot-setup-steps.yml currently use Node 20. There's no engine-strict setting in .npmrc/pnpm config, so installs won't hard-fail, but this is worth noting: if we ever enable strict engine checks, or if a future jotai patch relies on Node 22+ runtime APIs, this could break. Not a blocker for this bump, but you may want to plan a Node version upgrade separately.
• ESM-only build — Vite already consumes ESM natively, so no bundler changes needed.

No code changes made since nothing in our usage triggers the removed/changed APIs.