Skip to content

0.8.0 publication: sign one release for both stable and canary #335

Open

Description

@andersalm

Part of #93. Found by the 10 Oct review of develop.

Decision (OMP, by Occam): 0.8.0 is one signed release published on both channels. Canary Homes keep updating on canary; new users and re-trusted 0.7.x Homes use stable. No channel-promotion code.

Today: updates require an exact channel match (update.rs:122,176-187), the installer refuses a different channel (update.rs:734), release-publish.sh signs canary only (:198,:289), and the signer signs stable only from a v* tag on main (release-signer.py:322-357). elastos/Cargo.toml is 0.7.1.

Done means

  • release-publish.sh has a stable mode that prepares the same packages for the v0.8.0 tag on main; one signed stable release, which canary Homes also accept (12 Oct decision).
    Preparation done (source): train a678c17f6 scripts/release-publish.sh:114-116,244-247; rehearsal PASS.
  • elastos/Cargo.toml is 0.8.0 at the tag.
  • Proof on the seed: a canary Home updates to 0.8.0; a fresh stable install gets 0.8.0.

Activity

  1. added this to the 0.8.0 milestone on Oct 10, 2026
  2. self-assigned this
    on Oct 15, 2026
  3. andersalm commented on Oct 16, 2026

    @andersalm
    ContributorAuthor

    Remaining for 0.8.0 (15 Oct 22:45 COT; final candidate alpha.21 = alpha.20 + automatic Community recovery; plan #93 6207232773): at publication: #375 merges with its PR run green on the alpha.21 SHA, tag v0.8.0 on that SHA, prepare, sign and publish stable; proof: a canary Home updates to 0.8.0 in System and a fresh stable install gets 0.8.0.

  4. andersalm commented on Oct 17, 2026

    @andersalm
    ContributorAuthor

    The owner corrected both helper findings. record-dry-check.py (SHA256 cee85174e8b1f198c571206b44f83d4280c5e6eae9aaebcb15017cfac5c1a7b5) now requires the exact non-empty source platform set and explicitly reports record-mapping scope.
    rehearsal-335.py (SHA256 725b7aec0ce67ce403b891f0b75de80b8de0000d14ae7287f0ae5d73e528cb2f) adds error/signal cleanup and Runtime hash binding. Owner fixtures refused empty/partial sets with exit 1 and confirmed work-directory removal after missing-Runtime failure and SIGTERM (exit 143).
    Independent agent source review PASS; the full rehearsal against the qualified package Runtime, normal signer admission and installed acceptance remain required.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions