Skip to content

Select and verify the Apple Silicon release for the focused preview #10

Open

Description

@lastobelus

Outcome

The focused preview points to one tested, immutable Apple Silicon GitHub release built from the exact commit accepted at the preview gate. The release may be stable or marked as a prerelease, but it must be visibly and honestly labeled as an early preview.

Acceptance criteria

  • Application and package versions are bumped together.
  • The tag identifies the exact commit that passed the preview gate.
  • The Apple Silicon artifact and every published checksum are verified after download.
  • The release is visibly labeled as an early preview at the download point.
  • Release notes state audience, Apple Silicon compatibility, exact trial command, meaningful changes, limitations, signing/notarization status, and rollback target.
  • The previous known-good artifacts remain available.
  • Native Intel availability is not implied; issue Ship and validate native Intel releases for the broad announcement #80 owns Intel release activation at Broad announcement.

Current candidate

Published v0.1.3 provides a valid immutable Apple Silicon artifact and portable CLI. Issue #11 may use it immediately for clean-machine Silicon validation. This issue remains open until the focused-preview gate confirms whether v0.1.3 is the final preview candidate or a newer exact-main release is required.

Activity

  1. added this to the Focused preview milestone on Aug 3, 2026
  2. self-assigned this
    on Aug 3, 2026
  3. added
    releaseRelease engineering and distribution
    launch:blockerBlocks the next Markover announcement gate
    launchWork required for an announcement or release gate
    on Aug 3, 2026
  4. lastobelus commented on Aug 7, 2026

    @lastobelus
    OwnerAuthor

    Removed completed annotation-contract issue #7 from this issue’s blockers. PRs #47, #48, and #49 satisfy the focused-preview interpretation contract and representative-control requirement. The remaining live/cross-model evaluation work in #46 belongs to the Broad announcement milestone and does not block cutting the focused-preview prerelease.

  5. changed the title [-]Cut a current-main prerelease for the focused preview[/-] [+]Cut a current-main Apple Silicon prerelease for the focused preview[/+] on Aug 7, 2026
  6. changed the title [-]Cut a current-main Apple Silicon prerelease for the focused preview[/-] [+]Select and verify the Apple Silicon release for the focused preview[/+] on Aug 7, 2026
  7. lastobelus commented on Aug 7, 2026

    @lastobelus
    OwnerAuthor

    Candidate release available

    v0.1.3 is now the current valid Apple Silicon candidate and is explicitly labeled early preview at the download point. The issue no longer requires GitHub's prerelease flag: a stable immutable release is acceptable if it is the exact candidate accepted when the focused-preview gate closes.

    #11 no longer waits on this issue and may test v0.1.3 now. This issue remains open because #6, #9, and #39 still determine whether v0.1.3 is the final preview candidate or a newer exact-main version is needed.

  8. lastobelus commented on Aug 8, 2026

    @lastobelus
    OwnerAuthor

    Issue #9 documentation handoff

    Issue #9 is review-ready at cb52d5e. Its public URLs remain stable when the audience-root change lands.

    For the final focused-preview release decision and notes, preserve this user-facing checklist:

    • label the release Early macOS preview and identify its intended audience;
    • state macOS 14 Sonoma or newer on Apple Silicon, plus Node.js 22.13.0 or newer for the launcher;
    • use the exact trial command from the README;
    • say the app is hardened and ad-hoc signed, but not Apple-verified or notarized;
    • do not imply native Intel availability; issue Ship and validate native Intel releases for the broad announcement #80 owns that Broad-announcement activation;
    • link Privacy, storage, and recovery, Markdown support and preview limitations, and GitHub Discussions;
    • state the early-preview format caveat: historical JSON and attachments are preserved, but a newer Markover may not open every older review;
    • if mentioning durability, keep the tested boundary: while Markover is responsive and local storage is healthy, managed changes have a two-second default app-process-crash window; power, OS, hardware, and unhealthy or unusually slow storage are excluded; and
    • retain the exact rollback target and trust/provenance facts from the release runbook.

    The source guide and user/developer split are pending merge from the issue #9 branch; this comment is the dependency handoff, not a claim that the new Pages content is deployed yet.

  9. lastobelus commented on Aug 8, 2026

    @lastobelus
    OwnerAuthor

    v0.1.3 independent public-download preflight

    Issue #11's preparation evidence independently verifies the downloaded-artifact criterion for the current v0.1.3 candidate:

    • all four public release assets downloaded successfully;
    • the app ZIP and CLI payload matched their published checksum sidecars and locally computed digests;
    • both payload attestations verified against the exact release workflow, tag, source commit, and GitHub-hosted-runner constraint;
    • a released CLI invocation using fresh isolated npm and Markover caches resolved v0.1.3, downloaded and validated the arm64 app, wrote the expected validation marker, and reused that cache on the second run;
    • extracted app inspection confirmed version 0.1.3, arm64-only Mach-O files, the macOS 14 floor, hardened ad-hoc signing, and a valid deep/strict code seal.

    The corresponding acceptance checkbox is now complete. This evidence came from the occupied maintainer profile and intentionally stopped before app launch, so it does not prove quarantine, Gatekeeper override, or the end-to-end clean-profile workflow. #11 remains blocked on the #93 batch session. If the focused-preview gate selects a release newer than v0.1.3, repeat this verification against that exact replacement before closing #10.

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

Metadata

Metadata

Assignees

Labels

launchWork required for an announcement or release gatelaunch:blockerBlocks the next Markover announcement gatereleaseRelease engineering and distribution

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions