Skip to content

release: implement fork-owned tag-only desktop release workflow #2

Closed

Description

@ag-jin

Owner boundary

.github/workflows/release.yml and release operations documentation.

Dependency

Blocked by #1: fork-owned release identity and configuration contract.

Goal

Create a fork-safe release graph that checks out an immutable fork tag, builds selected desktop installers on fork-available runners, and uploads one GitHub Release with updater metadata and checksums.

Public seams

  • .github/workflows/release.yml
  • docs/operations/release.md
  • desktop updater metadata generated in release/

Acceptance criteria

  • Stable release jobs are tag-only; the three-hour scheduled nightly trigger is removed from the fork workflow.
  • Every build job checks out the selected immutable tag SHA.
  • Runner labels resolve in the fork account.
  • Release assets include selected installers, updater manifests, blockmaps, and checksums.
  • GitHub Release publication uses only fork-owned release authority and repository slug.
  • No step reaches upstream domains, credentials, npm package identity, or version-bump authority.

Verification

  • vp fmt --check .github/workflows/release.yml docs/operations/release.md
  • git diff --check
  • Run a dedicated prerelease tag and read back the GitHub Release assets in Chrome.

Blocks

Signing and end-to-end release verification.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions