bahmcloud_store/CHANGELOG.md

Changelog

All notable changes to this repository will be documented in this file.

Sections:

• Added
• Changed
• Fixed
• Removed
• Security

---

[0.3.1] - 2026-01-15

Fixed

• Panel header version is now derived from manifest.json via backend API (no more hardcoded version strings).
• Mobile navigation/header visibility improved by explicitly disabling iframe embedding for the custom panel.
• When adding a custom repository without a display name, the name is now fetched from the git provider (GitHub/Gitea) and shown automatically.

[0.3.0] - 2026-01-15

Added

• Repository enrichment for the Store UI:
  • GitHub: fetch owner and description via GitHub REST API.
  • Gitea: fetch owner and description via Gitea REST API (/api/v1).
• Provider detection for GitHub/GitLab/Gitea (best-effort).
• Automatic UI description line populated from provider data (when available).

Changed

• Panel module URL cache-busting updated to avoid stale frontend assets.

Fixed

• Store "Refresh" now triggers immediate backend refresh (from 0.2.0).
• Avoided circular imports by using TYPE_CHECKING for type references.

Notes

• Installation/README details view/update entities will be added in later versions.

[0.2.0] - 2026-01-15

Added

• Foundation architecture for BCS (Bahmcloud Component Store) inside a Home Assistant custom component.
• Custom panel (no iframe) using hass.callApi() to avoid authentication issues.
• Store index loader (store.yaml) with periodic refresh (data only).
• Manual repository management:
  • Add repository
  • List repositories
  • Remove repository Persisted via Home Assistant storage (.storage/bcs_store).
• Public static asset endpoint for panel JS (/api/bahmcloud_store_static/...) without auth (required for HA custom panels).
• Initial API namespace:
  • GET /api/bcs list merged repositories (index + custom)
  • POST /api/bcs add custom repository
  • DELETE /api/bcs/custom_repo remove custom repository

Changed

• Store API/UI terminology standardized to "BCS" (Bahmcloud Component Store), while integration domain remains bahmcloud_store for compatibility.

Notes

• Installation, README rendering, provider enrichment (GitHub/Gitea/GitLab), and Update entities will be implemented in later versions.