[github-actions]

🤖 I have created a release beep boop

3.17.1 (2026-10-29)

🐛 Bug Fixes

• notifications: show loading after login with empty inbox (#3935) (8c61f45)
• pnpm lockfile duplicate (681125d)

📚 Documentation

• Update Wakatime badge link in README.md (2fee4a1)

🤖 Continuous Integration

• labeler: accept breaking-change markers and broader PR title scopes (#3971) (75c476f)
• labeler: accept breaking-change markers in PR titles (75c476f)

🧪 Testing

• remove nock in favour of axios mocks (#3976) (b0a4288)

📦 Dependency Updates (Core)

• deps-core: update @atlaskit/avatar to v30.0.5 (#3926) (8a8fd9c)
• deps-core: update @atlaskit/avatar-group to v14.4.6 (#3927) (c0066aa)
• deps-core: update @atlaskit/button to v25.4.8 (#3902) (d51f9e6)
• deps-core: update @atlaskit/button to v25.5.0 (#3931) (9098847)
• deps-core: update @atlaskit/button to v25.6.0 (#3946) (87e8249)
• deps-core: update @atlaskit/button to v25.6.1 (#3964) (b3b07e1)
• deps-core: update @atlaskit/css to v1.1.7 (#3903) (28bc259)
• deps-core: update @atlaskit/form to v18.2.1 (#3939) (5e5367c)
• deps-core: update @atlaskit/inline-message to v16.4.8 (#3928) (5b5f65f)
• deps-core: update @atlaskit/modal-dialog to v17.1.0 (#3918) (eb7bddd)
• deps-core: update @atlaskit/modal-dialog to v17.1.1 (#3940) (b9c2a11)
• deps-core: update @atlaskit/primitives to v22.6.0 (#3911) (80b8bc2)
• deps-core: update @atlaskit/select to v23.1.3 (#3904) (462cf59)
• deps-core: update @atlaskit/tokens to v20.6.1 (#3912) (fd6e323)
• deps-core: update @atlaskit/tokens to v20.7.0 (#3961) (65cc7fa)
• deps-core: update @atlaskit/tooltip to v24.4.2 (#3955) (0dd9a53)
• deps-core: update @tanstack/react-query to v5.104.3 (#3905) (60f956d)
• deps-core: update @tanstack/react-query to v5.104.4 (#3917) (f765b63)
• deps-core: update @tanstack/react-query to v5.104.5 (#3932) (43b6bef)
• deps-core: update electron to v44.8.0 (#3913) (2f64f3d)
• deps-core: update electron to v44.9.0 (#3919) (fcf8f5a)
• deps-core: update electron to v44.9.1 [security] (#3937) (01a953b)
• deps-core: update electron to v45 (#3952) (64937d6)
• deps-core: update electron-menubar to v11.1.2 (#3936) (8cf4463)
• deps-core: update electron-updater to v6.8.11 (#3942) (c2e0d93)

📦 Dependency Updates (Other)

• deps: lock file maintenance (#3900) (4aaf12c)
• deps: lock file maintenance (#3916) (63688f2)
• deps: lock file maintenance (#3924) (ffad5ae)
• deps: lock file maintenance (#3953) (ef55960)
• deps: lock file maintenance (#3954) (f5eb161)
• deps: update @biomejs/biome to v2.6.3 (#3947) (0e550bc)
• deps: update @graphql-codegen/typescript-operations to v6.2.0 (#3974) (e4a1664)
• deps: update cn to v0.5.0 (#3920) (a6129c4)
• deps: update electron-builder to v26.18.0 (#3948) (0efa400)
• deps: update happy-dom to v21.0.3 (#3906) (efedda1)
• deps: update happy-dom to v21.0.4 [security] (#3938) (5d2eeb0)
• deps: update i18next to v26.4.7 (#3907) (8f12f5b)
• deps: update i18next to v26.5.10 (#3956) (5913fa2)
• deps: update i18next to v26.5.11 (#3972) (5b55985)
• deps: update i18next to v26.5.2 (#3921) (ad27a83)
• deps: update i18next to v26.5.3 (#3934) (ac1496d)
• deps: update i18next to v26.5.5 (#3944) (2b68638)
• deps: update i18next-browser-languagedetector to v8.2.3 (#3957) (5da346a)
• deps: update i18next-cli to v1.77.0 (#3922) (dad1e07)
• deps: update i18next-cli to v1.79.1 (#3949) (42031f4)
• deps: update i18next-cli to v1.80.0 (#3962) (04cb28d)
• deps: update i18next-cli to v1.80.4 (#3965) (fd8e31c)
• deps: update node to v26 (#3975) (871e141)
• deps: update node.js to v24.22.1 (#3930) (4d06a02)
• deps: update pnpm to v12.14.0 (#3915) (a6011c8)
• deps: update pnpm to v12.15.0 (#3950) (56416e5)
• deps: update pnpm/setup action to v3.1.2 (#3958) (efe9136)
• deps: update react monorepo to v19.3.1 (#3908) (e34d433)
• deps: update react-i18next to v17.0.19 (#3909) (7eed1cc)
• deps: update react-i18next to v17.1.0 (#3923) (7afe51f)
• deps: update react-i18next to v17.1.8 (#3959) (1bad6b7)
• deps: update react-i18next to v17.1.9 (#3973) (bc58a7d)
• deps: update sonarsource/sonarqube-scan-action action to v8.4.0 (#3966) (87f6077)
• deps: update vite to v8.3.5 (#3945) (7d7fa62)
• deps: update vitest monorepo to v5.0.5 (#3910) (790bc6d)
• deps: update zizmorcore/zizmor-action action to v0.8.0 (#3951) (6c0a170)
• deps: update zustand to v5.0.16 (#3960) (b02b159)

🧹 Chore

• add devEngines Node.js pin (#3968) (5087087)
• declare pnpm via devEngines.packageManager (#3969) (f08a068)
• openspec update 1.15.0 (9b3a57e)
• sort devEngines keys (#3970) (c2fddad)

---

This PR was generated with Release Please. See documentation.

[netlify]

✅ Deploy Preview for atlassify canceled.

Name	Link
🔨 Latest commit	a622889
🔍 Latest deploy log	https://app.netlify.com/projects/atlassify/deploys/6ae29e8e62568b12ea0aa06d

[gitar-bot]

Code Review ✅ Approved 7 closed / 7 findings

🟢 Low risk · This release updates version metadata and adds changelog entries only; it does not change application code or runtime behavior.

Release-please bump to 3.17.1 with changelog entries for bug fixes, labeler updates, and dependency refreshes. Seven release-commit dependency reverts that had desynced the lockfile, including i18next, @atlaskit/avatar, electron, electron-updater, @atlaskit/modal-dialog, and @atlaskit/button, have been addressed. No open issues remain.

✅ 7 closed

✅ Bug: Release commit downgrades i18next 26.5.2→26.4.7, mismatching lockfile

📄 package.json:65
The parent commit ad27a83 (#3921) moved i18next to 26.5.2, and pnpm-lock.yaml still resolves i18next@26.5.2. This release commit puts package.json back to 26.4.7. Release-please most likely built the version bump from an older package.json and overwrote the newer dependency. Once this merges, package.json and the lockfile disagree, so pnpm install --frozen-lockfile in CI or release builds fails with ERR_PNPM_OUTDATED_LOCKFILE, or a non-frozen install quietly downgrades i18next. The CHANGELOG also leaves out the 26.5.2 update. Fix: rebase or regenerate the release PR so that only the version field changes and i18next stays at 26.5.2.

✅ Bug: Release commit reverts @atlaskit/avatar 30.0.5→30.0.4, desyncs lockfile

📄 package.json:74
The release commit sets @atlaskit/avatar back to 30.0.4 in package.json. That undoes #3926 (8a8fd9c), which had bumped it to 30.0.5. pnpm-lock.yaml still has specifier: 30.0.5 for the importer (line 210), so pnpm install --frozen-lockfile will fail in CI and release builds because the lockfile no longer matches package.json. This is the same stale-base problem as the i18next downgrade from the earlier review: release-please appears to have built this commit from an outdated package.json. The 30.0.5 bump is also missing from the changelog. Fix: restore "@atlaskit/avatar": "30.0.5", or regenerate the release PR from the current main.

✅ Bug: Release commit reverts electron 45.0.0→44.9.1, mismatching pnpm-lock

📄 package.json:124
The parent commit 64937d6 (#3952) bumped electron to 45.0.0 in both package.json and pnpm-lock.yaml. This release commit's package.json takes electron back to 44.9.1, but pnpm-lock.yaml still has specifier: 45.0.0 (pnpm-lock.yaml:359-361). Because of that mismatch, pnpm install --frozen-lockfile fails in CI and release builds, and the v45 upgrade gets silently dropped from 3.17.1. The CHANGELOG also has no entry for the electron v45 bump. This looks like the same stale-base problem that reverted i18next and @atlaskit/avatar in earlier findings. Fix: set electron back to 45.0.0 by regenerating the release-please PR from the current main.

✅ Bug: Release commit reverts electron-updater 6.8.11→6.8.9, out of sync with lockfile

📄 package.json:64
The release commit sets electron-updater back to 6.8.9. Main already moved it to 6.8.11 in c2e0d93 (#3942), and pnpm-lock.yaml still resolves electron-updater@6.8.11 (lines 184, 2762, 8173). The release-please branch was built from a stale package.json, so merging it would undo the dependency bump. It also leaves package.json and the lockfile disagreeing, which makes pnpm install --frozen-lockfile fail in CI. This is the same stale-branch problem as the earlier i18next/avatar/electron reverts. Fix it by rebasing or regenerating the release PR on current main, or by restoring 6.8.11.

✅ Bug: Release commit reverts @atlaskit/modal-dialog 17.1.1→17.1.0

📄 package.json:87
main already has @atlaskit/modal-dialog at 17.1.1 from #3940 (b9c2a11). This release commit sets package.json back to 17.1.0. The lockfile isn't touched here, so the manifest no longer matches it, and merging would ship the release with the older version, undoing the Renovate update. The CHANGELOG doesn't list the 17.1.1 bump either. It looks like the same stale-base regeneration problem that earlier caused the i18next, avatar and electron reverts. Fix: rebase or regenerate the release-please branch on current main, or set the pin back to 17.1.1.

...and 2 more closed from earlier reviews

Verification

Rules No rules evaluated

Functional validation Not enabled

Set up

_{For more verification details, comment gitar display:verbose.}

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing compact verification results.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Powered by Gitar — free for open source}

[github-actions]

🤖 Created releases:

• v3.17.1

🌻