[efraespada]

Adds a tag-triggered npm prerelease workflow that publishes the reviewed core and four adapters from successful CI artifacts for the same production commit. Registry hash checks and safe retries enable prerelease adoption while preserving the stable release acceptance gate.

What changed

• Retains verified package archives from production CI runs for use by the release workflow.
• Publishes the core and four adapters from matching v*-next.* tags through npm Trusted Publishing, verifying registry hashes and supporting partial-release retries.
• Documents Trusted Publisher setup, prerelease publishing and recovery, and stable release evidence requirements.
• Allows prerelease publication before installed application acceptance while retaining that requirement for stable publication.

Validation

• The author reports validating the complete source suite and coverage, TypeScript and Svelte checks, the specification catalog, workflow syntax, and the public registry reader.

Review notes

• Configure npm Trusted Publishing for each of the five package coordinates using the npm_release.yml workflow and npm environment before the first publication.

Closes #11

[docs-page]

To preview the documentation for this pull request, visit the following URL:

docs.page/vypdev/ha-ui~12

Documentation is deployed and generated using docs.page

[vypbot]

Current status: All findings originating in this review are resolved.
Last reconciled on 56656b5. See aggregate Bugbot status.

🤖 Bugbot review snapshot

Bugbot reported 1 potential problem when commit d85aa2d was analyzed. This snapshot is historical; use the status block above for current state. 1 finding is linked to changed code.

Findings

• low: Reject prerelease tags with invalid SemVer numeric components — tooling/npm-prerelease.mjs:37

[vypbot]

Bugbot: review complete

Current status: No active findings on 56656b5.

Pull request · Verified commit · Workflow run

[vypbot]

Copilot approval · Human review needed

Status: A protected workflow, policy, or trust-boundary file changed.
Completed: 1/1 observed checks succeeded; Bugbot complete.
Action required: Ask a human reviewer to decide.
Impact: No new approval is confirmed for this revision.
See checks

Technical evidence

Revision: 56656b594cb0; base: be489fa4859f; reason: protected-path.