build(deps-dev): bump jotai-devtools from 0.10.1 to 0.13.0 in /console

[dependabot]

Bumps jotai-devtools from 0.10.1 to 0.13.0.

Release notes

Sourced from jotai-devtools's releases.

Release 0.13.0

0.13.0 (2025-09-13)

• chore: update dependencies (#204) (79b8a84), closes #204
• refactor: support INTERNAL_buildStoreRev2 + drop support for older version (#201) (0dcf91b), closes #201
• fix: building blocks are included on devStore (#198) (3ca38db), closes #198
• fix: remove direct dependency to jotai (#190) (5a44e7f), closes #190

Release 0.12.0

0.12.0 (2025-04-27)

• fix: re-add dev only export + add warning + docs around tree shaking (#186) (9835e66), closes #186
• chore: update dependencies (#185) (9982bf2), closes #185
• refactor: drop support for dev_* methods (#180) (2ab02e2), closes #180

Release 0.11.0

0.11.0 (2025-02-19)

• fix: drop support for jotai store v1 (#173) (5c19880), closes #173
• fix: guard restore action with isTimeTravelling atom (#174) (8a2d303), closes #174
• test(TimeTravel): async atom snapshot history (#170) (efd498b), closes #170
• chore: update dependencies (#172) (32dec78), closes #172
• docs: fix readme. (#162) (12adbab), closes #162

Changelog

Sourced from jotai-devtools's changelog.

0.13.0 (2025-09-13)

• chore: update dependencies (#204) (79b8a84), closes #204
• refactor: support INTERNAL_buildStoreRev2 + drop support for older version (#201) (0dcf91b), closes #201
• fix: building blocks are included on devStore (#198) (3ca38db), closes #198
• fix: remove direct dependency to jotai (#190) (5a44e7f), closes #190

0.12.0 (2025-04-27)

• fix: re-add dev only export + add warning + docs around tree shaking (#186) (9835e66), closes #186
• chore: update dependencies (#185) (9982bf2), closes #185
• refactor: drop support for dev_* methods (#180) (2ab02e2), closes #180

0.11.0 (2025-02-19)

• fix: drop support for jotai store v1 (#173) (5c19880), closes #173
• fix: guard restore action with isTimeTravelling atom (#174) (8a2d303), closes #174
• test(TimeTravel): async atom snapshot history (#170) (efd498b), closes #170
• chore: update dependencies (#172) (32dec78), closes #172
• docs: fix readme. (#162) (12adbab), closes #162

Commits

• ea6cac0 chore: release v0.13.0
• 79b8a84 chore: update dependencies (#204)
• 0dcf91b refactor: support INTERNAL_buildStoreRev2 + drop support for older version (#...
• 3ca38db fix: building blocks are included on devStore (#198)
• 5a44e7f fix: remove direct dependency to jotai (#190)
• 54889d3 chore: release v0.12.0
• 9835e66 fix: re-add dev only export + add warning + docs around tree shaking (#186)
• 9982bf2 chore: update dependencies (#185)
• 2ab02e2 refactor: drop support for dev_* methods (#180)
• fadae1c chore: release v0.11.0
• Additional commits viewable in compare view

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)

[github-actions]

Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone.

PR title guidelines

• Use imperative mood: "Fix X" not "Fixed X" or "Fixes X"
• Be specific: "Fix panic in catalog sync when controller restarts" not "Fix bug" or "Update catalog code"
• Prefix with area if helpful: compute: , storage: , adapter: , sql:

Pre-merge checklist

• The PR title is descriptive and will make sense in the git log.
• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).