Skip to content

v1 Unit 6: Canary migration #55

Description

@mairas

Part of the shared-workflows v1 plan (tracking issue: issue 49).

Goal: Prove v1 on one repo per kind before the major tag moves.

Requirements: R6, R7

Dependencies: Units 2–4 on an rc tag

Canaries: halos-org/halos-browser-trust (halos-org deb), hatlabs/halos-halpi-desktop-branding (hatlabs deb, no tests job), halos-org/skip-freeboard-panel (npm), halos-org/docs-tools (tag-only; lands after docs-tools PR 31), hatlabs/signalk-halpi (deb + npm, cross-org; after skip-freeboard-panel publishes).

Approach: One PR per canary pinned to @v1.0.0-rc.N, using the Unit 7 per-repo procedure. Verify the main run and a published release. After Unit 5, a second PR repins to @v1; it is required even when v1.0.0 equals the last rc commit, because the ref string differs. Each canary merge cuts a new +N pre-release and an unstable dispatch; that is accepted.

signalk-halpi builds with an explicit npm run build and has no prepublishOnly. Its migration PR adds the lifecycle script so publish-npm.yml needs no build input. In its release.yml, apt-publish and publish-npm are independent; a failed npm publish after a successful APT dispatch is not rolled back and is re-run by hand.

Test expectation: covered by Units 2–4 scenarios executed on these repos.

Verification: Each canary has one green PR, one release equivalent to its previous release, and protection requiring status.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions