🔧🧑‍💻 - Automate npm releases for the ha ui package cohort #11

Activity

1. efraespada

   added

   choreLabel to manage chore branchesLabel to manage chore branches

   maintenanceLabel to manage maintenance branchesLabel to manage maintenance branches

   in-progressStart work on an admitted issue.Start work on an admitted issue.

   priority: lowLabel to indicate a priority lowLabel to indicate a priority low

   on Nov 5, 2026
2. vypbot

   added

   state:ai-processingA Copilot agent is analyzing or working on the issue or change.A Copilot agent is analyzing or working on the issue or change.

   on Nov 5, 2026
3. vypbot

   assigned

   efraespada

   on Nov 5, 2026
4. vypbot

   added the

   Maintenance

   issue type on Nov 5, 2026
5. vypbot

   added this to vypdevon Nov 5, 2026
6. vypbot

   moved this to Todo in vypdevon Nov 5, 2026
7. vypbot

   moved this from Todo to In Progress in vypdevon Nov 5, 2026
8. vypbot

   added

   branchedThe linked branch and required SDD commit are verified.The linked branch and required SDD commit are verified.

   on Nov 5, 2026
9. vypbot

   changed the title [-]Automate npm releases for the ha-ui package cohort[/-] [+]🔧🧑‍💻 - Automate npm releases for the ha ui package cohort[/+] on Nov 5, 2026
10. vypbot

    added

    state:workingWork can proceed on the verified branch or without a branch.Work can proceed on the verified branch or without a branch.

    and removed

    state:ai-processingA Copilot agent is analyzing or working on the issue or change.A Copilot agent is analyzing or working on the issue or change.

    on Nov 5, 2026
11. vypbot commented on Nov 5, 2026

    

    vypbot

    on Nov 5, 2026

    More actions

    Implementation plan

    Current status: Ready to start. No action is required from maintainers before implementation.

    1. Define the release contract
       • Inventory the package coordinates and resolve the stated count: Lit and DOM core plus four adapters is six packages.
       • Document version/tag rules, the stable consumer evidence gate, and the `0.1.0-next.1` prerelease path.
    2. Add a dedicated tag publisher
       • Create a product-owned GitHub Actions workflow triggered only by reviewed release tags; keep it independent of Copilot workflows.
       • Use npm Trusted Publishing for each package coordinate and grant publication only to this workflow.
    3. Build and verify release archives
       • Build all packages from the tag and validate the existing reproducible archives and package metadata before any publish step.
       • Run artifact and publication-policy checks in CI without publishing from pull requests.
    4. Publish core, then adapters safely
       • Publish the Lit and DOM core packages first, then publish React, Vue, Angular, and Svelte adapters with framework peers and exact core-version dependencies.
       • Before each publish, detect existing versions and skip matching published packages so a retry resumes partial releases without overwriting.
    5. Verify registry state and document recovery
       • After publication, compare npm registry integrity for every package version with the verified archive; fail the release if any digest differs.
       • Document maintainer setup for each Trusted Publisher coordinate, partial-release retry steps, and the stable consumer evidence gate.

    Acceptance: A CI run for the reviewed `0.1.0-next.1` tag verifies reproducible archives, publishes core before all four adapters under npm tag `next`, and confirms registry integrity for all six package coordinates; a retry after a partial publish skips already-published versions, and pull-request runs publish nothing.

    Need something else? Mention the bot with a question or use /copilot help.
12. 2 remaining items

    Load more
13. vypbot

    added

    65%Progress: 65%Progress: 65%

    and removed

    state:ai-processingA Copilot agent is analyzing or working on the issue or change.A Copilot agent is analyzing or working on the issue or change.

    on Nov 5, 2026
14. vypbot commented on Nov 5, 2026

    

    vypbot

    on Nov 5, 2026

    Last edited by vypbot

    More actions

    Issue closed — historical progress

    Current status: closed as completed.

    The last estimate is retained below as history. Closure does not certify a new percentage, tests, or branch alignment.

    Action required: none for this closed issue. If work continues, reopen the issue; a fresh assessment can update this same card.

    Last assessment before closure (historical)

    Progress: 75% — in progress

    > Current status: [R1] Automate the release of the five versioned packages from the same reviewed GitHub tag: the Lit and DOM core and the React, Vue, Angular, and Svelte adapters. Use npm Trusted Publishing from GitHub Actions. Build and verify the existing reproducible archives before publication, publish the core first, confirm the npm registry integrity of every version, and resume a partial release safely without overwriting packages. Keep the product workflow independent of the installed Copilot workflows. — The source adds a product-owned tag workflow, uses npm Trusted Publishing, retrieves CI-retained archives, and implements core-first publication with version and registry-digest checks plus safe recovery. The adapters are included in the shared package cohort. Source patches do not verify that the workflow ran or that registry publishing succeeded.
    [R2] Publish the verified 0.1.0-next.1 prerelease under the next tag so Domus can pin the core by exact version. Keep the existing stable consumer evidence gate. All four adapters must remain independently installable with their framework peers and the exact core version. CI must verify artifacts and the publication policy without publishing on a PR. — The workflow accepts v0.1.0-next.1-style tags and publishes with npm tag next; policy code allows prerelease publication without stable consumer receipts while retaining those receipts for stable releases. CI retains artifacts only on production pushes,
    [untrusted content truncated]

    Next: [R3] "acceptance": "A CI run for the reviewed 0.1.0-next.1 tag verifies reproducible archives, publishes core before all four adapters under npm tag next, and confirms registry integrity for all six package coordinates; a retry after a partial publish skips already-published versions, and pull-request runs publish nothing." — Verify an actual successful CI and tag run for 0.1.0-next.1, including reproducible archive checks, core-first publication of all six coordinates under next, matching registry integrity, a retry that skips already-published versions, and no publication on pull requests.
15. efraespada

    linked a pull request that will close this issueci: publish the verified npm prerelease cohort #12on Nov 5, 2026
16. vypbot

    added

    state:ai-processingA Copilot agent is analyzing or working on the issue or change.A Copilot agent is analyzing or working on the issue or change.

    75%Progress: 75%Progress: 75%

    and removed

    65%Progress: 65%Progress: 65%

    state:ai-processingA Copilot agent is analyzing or working on the issue or change.A Copilot agent is analyzing or working on the issue or change.

    on Nov 5, 2026
17. vypbot commented on Nov 5, 2026

    

    vypbot

    on Nov 5, 2026

    Last edited by vypbot

    More actions

    Issue closed: synchronization recommendation retired

    No branch synchronization is required for this closed issue.

    The previous recommendation is historical. Issue closure does not certify that the branches are synchronized.
18. vypbot

    closed this as completedon Nov 5, 2026
19. vypbot

    removed

    in-progressStart work on an admitted issue.Start work on an admitted issue.

    on Nov 5, 2026
20. github-project-automation

    moved this from In Progress to Done in vypdevon Nov 5, 2026
21. vypbot

    added

    100%Progress: 100%Progress: 100%

    and removed

    state:workingWork can proceed on the verified branch or without a branch.Work can proceed on the verified branch or without a branch.

    75%Progress: 75%Progress: 75%

    on Nov 5, 2026