Skip to content

release: v0.3.0 GA - #12

Merged
jpettitt merged 1 commit into
mainfrom
release/v0.3.0
May 24, 2026
Merged

jpettitt merged 1 commit into
mainfrom
release/v0.3.0

Conversation

@jpettitt

Copy link
Copy Markdown
Owner

Summary

Consolidates the v0.3.0a1 / a2 / a3 alpha line into the v0.3.0 GA release. Version bumps across manifest.json, frontend/package.json, the lockfile, and INTEGRATION_VERSION. README overhauled for the GA reader: status callout, "What's new in v0.3" feature summary, new "Breaking changes from v0.2" section, dropped (v0.3+) qualifiers throughout, refreshed Roadmap. Fresh consolidated v0.3.0 entry in CHANGELOG.md with a full upgrade summary for users coming from v0.2.x. Includes the Gemini review's update (docs/review.md) marking every recommendation as RESOLVED / SHIPPED / DOCUMENTED.

Highlights for the GA reader

What's new since v0.2:

  • Per-rule background chip (background_color) — Mushroom-style colored circle behind the icon
  • Field-level priority merging — replaces v0.2 "winner takes all"; per-field merge with sentinel-aware release
  • YAML editing on ha-code-editor (CodeMirror 6) — syntax highlighting, entity autocomplete, Ctrl+S
  • Rule editor: HA-native form elements, paired foreground/background color picker, plain-English threshold comparator labels
  • Glob-target resolution cache — O(1) cache hits replace O(rules × globs × entities) fnmatch for large installs
  • Visual examples in docs/examples.md with theme-aware light/dark icons
  • README "See it in action" preview + developer notes section

Breaking changes from v0.2:

  • Template mode is removed. Stored mode: template rules drop on load.
  • Priority is now field-level. Users who depended on "highest-priority rule erases everything else" should set explicit null / "inherit" sentinels on fields they want released.
  • Outline toggle / options WS commands / outline_enabled storage field are all gone (replaced by per-rule chip).

Test plan

  • pytest tests/ — 118 pass
  • npm test (web-test-runner) — 104 pass
  • npm run typecheck — clean
  • npm run build — bundles produced
  • CI green on PR
  • After merge: release.yml runs pytest gate + publishes smart_icons.zip + auto-extracts the v0.3.0 section from CHANGELOG as release notes

Post-merge plan

Tag v0.3.0 on the merge commit; existing release.yml workflow handles the build + GitHub release + HACS-conventional zip layout.

Consolidate the v0.3.0a1/a2/a3 alpha line into a single GA release.
Bumps in manifest.json, frontend/package.json + lockfile, and
websocket_api INTEGRATION_VERSION (0.3.0a3 -> 0.3.0).

README rewritten:

- Status callout updated to v0.3.0 GA.
- "What's new in 0.2" replaced by "What's new in v0.3" with the
  consolidated feature list (background chip, field merge,
  ha-code-editor, native form elements, glob cache, visual
  examples, dev notes).
- New "Breaking changes from v0.2" section covering template-mode
  removal, the priority-merge semantic shift, and the outline-
  toggle removal.
- (v0.3+) qualifiers dropped from the Background chips section,
  the smart_icons_background attribute description, and the
  Priority bullet — v0.3 is the active line.
- Roadmap refreshed: v0.3 deliverables removed (shipped), v0.4+
  items consolidated.

CHANGELOG.md gains a v0.3.0 entry: a self-contained upgrade
summary for users coming from v0.2.x, covering breaking changes,
the feature set, bug fixes, internals, and migration steps. The
v0.3.0a1/a2/a3 entries are kept below for development history.

docs/review.md updated to mark all of the Gemini review's
recommendations as RESOLVED / SHIPPED / DOCUMENTED — they all
landed in the v0.3 cycle. Includes the AntiGravity (Gemini 3.5)
attribution and resolution annotations.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@jpettitt
jpettitt merged commit a61a85e into main May 24, 2026
2 checks passed
@jpettitt
jpettitt deleted the release/v0.3.0 branch May 24, 2026 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant