v0.14.0b6

[ErikBjare]

These are the release notes for ActivityWatch version v0.14.0b6.

New to ActivityWatch? Check out the website and the README.

Installation

See the getting started guide in the documentation.

Downloads

• Windows (.exe, installer)
• macOS (.dmg)
• Linux (.zip)

Contributors

Thanks to everyone who contributed to this release:

@ErikBjare, @TimeToBuildBob

Changelog

Changes since v0.14.0b5:

📦 activitywatch

✨ Features (1)

• feat(research): bake profile=research, port 5667 and a distinct bundle id into research builds (#1434) (e68707f)

🐛 Fixes (3)

• fix(research): emit colors on the study category preset (#1441) (25145ce)
• fix(package): resolve edition-suffixed Inno Setup output name (#1436) (774172f)
• fix(research): retain approved application names (#1431) (e36a4e4)

🔨 Misc (1)

• test(release): cover Windows research installer collection (#1438) (35017ff)

(excluded 2 less relevant commits)

📦 aw-watcher-window

🐛 Fixes (1)

• fix(research): recognize original browser aliases (#142) (a101165)

🔨 Misc (1)

• test(config): skip research-edition guards when AW_RESEARCH_EDITION=true (#143) (abd69a6)

📦 aw-qt

✨ Features (1)

• feat(autostart): preserve named profile at login (#133) (a4072df)

🐛 Fixes (1)

• fix(config): read isolated-root config.toml instead of config-<profile>.toml (#132) (e285e77)

📦 aw-tauri

✨ Features (1)

• feat(autostart): isolate named profile entries (#253) (924150c)

Full Changelog: v0.14.0b5...v0.14.0b6

---

This discussion was created from the release v0.14.0b6.

[TimeToBuildBob]

Thanks! Continuing the check I started on the v0.14.0b4 thread: the stale-aw-server pin in the Tauri builds (b4 shipped aw-server 0.13.1) stays fixed through b5/b6/b7.

How I checked it (build provenance, not a runtime test): for a given tag, compare the aw-tauri submodule's src-tauri/Cargo.lock aw-server git pin against the parent repo's aw-server-rust submodule pointer.

Tag	aw-server-rust gitlink in activitywatch	aw-server pin in aw-tauri/src-tauri/Cargo.lock	Match
v0.14.0b4	b2e2dee7	0.13.1 @ 7c33810c	❌ stale
v0.14.0b5	d2e7b803	0.14.0 @ d2e7b803	✅
v0.14.0b5-research	d2e7b803	0.14.0 @ d2e7b803	✅
v0.14.0b6	d2e7b803	0.14.0 @ d2e7b803	✅
v0.14.0b7 (tag; build queued)	b0fab735	0.14.0 @ b0fab735	✅

So a b6 desktop install should not hit the b4 0.13.1 installer problem. Caveat: this verifies what the builds are pinned to, not the runtime behaviour of the published binaries — a smoke run of the b6 Tauri installer is still the only way to confirm the shipped artifact.

Two smaller observations from the same pass:

• The submodule refs quoted in the b6 changelog match the pinned gitlinks (aw-qt e285e77, aw-tauri 924150c, aw-watcher-window abd69a6).
• v0.14.0b6 is one commit ahead of v0.14.0b5-research (#1441, study-category preset colours), so the most recent published research build predates that fix — a refreshed study build would need a recut. Flagging in case it matters for the study rollout; not assuming it does.