🚀 Release: v4.2.0

[github-actions[bot]]

🚀 New Release: v4.2.0

View full release and download on GitHub

---

TaskMate v4.2.0

✨ New

Per-card design styles (#539)
Every TaskMate card can now be themed independently with one of four visual styles, plus a global default that any card can inherit.

• Classic — the original TaskMate look (default; unchanged).
• Playroom — warm, rounded, picture-book styling.
• Console — dark, neon-accented, game-HUD styling.
• Clean Pro — minimal, flat, professional styling.

How to use it:

• Per card: pick a style from the new Design dropdown in each card’s visual editor, or set card_design: classic | playroom | console | cleanpro in YAML. Leave it on Global default (global) to follow the integration-wide setting.
• Global default: set once in the TaskMate admin panel; every card left on Global default updates together.

Design tokens are shadow-scoped per card, so mixing styles across a dashboard is safe and cards never leak styling into the rest of Home Assistant.

🐛 Fixed

first_come chores were invisible on child cards and task lists (#540)
A first_come (competitive, first-to-complete-wins) chore was hidden from the entire pool of children. The visibility filter treated every non-everyone assignment mode as a single-active-child rotation and gated the chore on a current-child match — but first_come never sets a single active child, so its identifier was always empty and the chore showed for nobody.

first_come chores are now treated like everyone for the who-can-see-it decision: the whole pool sees the chore until one member fills the shared single-winner quota, after which it disappears for everyone. The frontend mirrors the backend logic and clamps the quota to 1. (PR #541)

---

Full changelog: v4.1.0...v4.2.0

---

Upgrading

Update via HACS or by downloading the latest release and copying to /config/custom_components/taskmate/.

After updating, restart Home Assistant. Lovelace resources will update automatically on restart.

---

💬 Questions or issues with this release? Reply below or open an issue.