Skip to content

chore: promote verified dev to main for v1.0.42 #579

Description

@LeXwDeX

Why

The user requested reconciling remaining branches, integrating all required work into dev first, then promoting that verified content to main and publishing the next stable release. The dev integration is tracked by #576 and PR #577; this delivery covers the subsequent main promotion.

Scope

Promote the accepted dev tree containing the Goal and Hooks repairs, branch audit, v1.0.42 release notes, and SpecGit-record CI optimization to main. Preserve the tested product tree and all existing main history.

Approach

Start only after PR #577 is accepted and merged into dev. Branch from that actual dev commit, establish a fresh branch-based SpecGit binding, open the main promotion PR, and verify current-head CI plus SpecGit acceptance. Merge through the normal platform operation after acceptance. The already-authorized stable release is then executed using release-fork.yml on main, followed by tag, asset, checksum, and executable verification.

Acceptance

  • The promotion head contains the accepted dev integration and existing main history.
  • Product content matches the accepted dev candidate; only the delivery record differs.
  • Current-head required checks and SpecGit acceptance pass.
  • The PR is merged to main and the bound promotion issue is closed.
  • Release notes render as stable 1.0.42 without placeholders, ready for the authorized release workflow.

Release result

Completed on 2026-09-07. Dev PR #577 merged as c22bda51471f907994558890da3de799bbb49106; main PR #580 merged as cd055eb5fc9bef1a9a1cbf98a72293419ade9e41. Both deliveries passed current-head SpecGit acceptance before merge, and all bound issues are closed. The Goal and Hooks source commits are ancestors of main; dev and main product trees are identical apart from the delivery record.

Stable Latest release: graphagent-v1.0.42. The tag points to the exact main commit above; the release is neither draft nor prerelease.

The official three-platform build ran concurrently with main CI. Publication was held until the main test run, Typecheck, and CodeQL all passed. The verified workflow artifacts were then published as the formal release.

All five published assets were downloaded again. Every asset matches the verified build bytes and the platform SHA256 digest; all four archives pass SHA256SUMS. Six macOS installation checks pass, including signature validity and the tampered-copy negative control. The actual binary reports 1.0.42; its isolated loopback server returned healthy=true/version=1.0.42 and served the embedded HTML and JavaScript. The smoke server was stopped afterward. The template workflow validated all 16 templates from config commit 9743916ecd0690ee69f424321ab15265c4e59e2a against this releasing main commit.

Final remote-branch recheck found the same seven surviving origin branches, with only the authorized main/dev integration changing their heads. The original user worktree remains preserved.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions