release-maintainer

To repair a broken npm latest dist-tag, you move the existing tag pointer to the correct immutable version without republishing the artifact. The workflow enforces tag repair and rollback-by-dist-tag recovery to fix dist-tag breakage safely.

Canary to stable promotion requires enforcing correct tag and verification sequencing across npm, git, and GitHub Releases. The workflow applies a safety-first promotion policy, ensuring latest movement and version immutability are honored before finalizing.

Troubleshooting missing Desktop portable assets and stale checksums involves targeted partial failure recovery guidance. The workflow identifies whether assets or checksums are missing and remediates the breakdown without republishing immutable artifacts.

First-time npm bootstrap requires reading canonical release docs and repository workflows to build an operational state plan. The workflow uses local and remote checks with git, gh, and npm to establish a deterministic release plan before user-authorized publishing.

Smoke testing and real Desktop update drills act as verification gates before stable promotion. The workflow enforces these safety-first policies, running deterministic release scripts to verify the update path works before authorizing the final publish.

If a git tag is missing after a GitHub Release is created, you must follow partial failure recovery guidance to synchronize state. The workflow performs live state checks with git and gh to build an accurate release plan and remediate the missing tag.