Skip to content

docs: clarify macOS release workflow refs#97116

Merged
RomneyDa merged 4 commits into
mainfrom
docs/macos-release-skill-ref
Jun 26, 2026
Merged

docs: clarify macOS release workflow refs#97116
RomneyDa merged 4 commits into
mainfrom
docs/macos-release-skill-ref

Conversation

@RomneyDa

@RomneyDa RomneyDa commented Jun 26, 2026

Copy link
Copy Markdown
Member

What Problem This Solves

The macOS release skill made it easy to confuse the workflow ref shown in GitHub Actions with the source ref that the workflow checks out. It also did not make the two repos explicit enough: openclaw/openclaw owns the product release page, while openclaw/releases owns the restricted macOS signing/notarization/publish workflows.

Why This Change Was Made

This updates .agents/skills/release-openclaw-mac/SKILL.md with the exact public handoff command and explains the split between public OpenClaw validation and the release-ops publisher. The public validation should run from release/YYYY.M.PATCH so Actions displays the release branch, while the release-ops openclaw/releases publisher runs from its own trusted main workflow ref and selects public source through tag/source_ref inputs.

User Impact

Future macOS release recovery work has a copy-paste command that matches prior successful stable macOS handoff runs and a clear warning not to use --ref main or --ref vYYYY.M.PATCH for the public validation workflow. It also states that public handoff validation never uploads macOS assets, regardless of preflight_only, and that release-ops preflight/publish may pause at the protected mac-release environment for Vincent or another reviewer to approve.

Evidence

  • git diff --check
  • Confirmed macos-release.yml dispatch from --ref release/2026.6.10 created successful run 28269425203 with headBranch=release/2026.6.10 and headSha=aa69b12d0086b631b139c1435c9621a5783e3a40.
  • Confirmed OpenClaw macOS Publish has a real-publish guard requiring workflow ref refs/heads/main.
  • Confirmed OpenClaw macOS Publish uses protected environment mac-release in the build_sign_and_package job.

@openclaw-barnacle openclaw-barnacle Bot added size: XS maintainer Maintainer-authored PR labels Jun 26, 2026
@clawsweeper

clawsweeper Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs changes before merge. Reviewed June 26, 2026, 7:07 PM ET / 23:07 UTC.

Summary
The branch updates .agents/skills/release-openclaw-mac/SKILL.md to document public macOS handoff validation from the release branch, the openclaw/releases release-ops repo, and the mac-release approval gate.

PR surface: Docs +41. Total +41 across 1 file.

Reproducibility: yes. for the review finding: source inspection of the PR head shows the mac skill changed to openclaw/releases while the sibling release-maintainer skill still instructs the same macOS release flow to use openclaw/releases-private.

Review metrics: 1 noteworthy metric.

  • Release instruction surfaces: 1 updated, 1 stale sibling remains. The PR updates the mac release skill, but the release-maintainer skill used in the same stable release workflow still carries old repo commands.

Merge readiness
Overall: 🦐 gold shrimp
Proof: 🦞 diamond lobster
Patch quality: 🦐 gold shrimp
Result: needs maintainer review before merge.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

  • Align .agents/skills/release-openclaw-maintainer/SKILL.md with the openclaw/releases macOS release-ops path or get release-owner confirmation for a documented split.

Risk before merge

  • [P1] Merging only the mac skill update leaves two release skills disagreeing about the release-ops macOS workflow repo, so a release operator could follow the stale sibling runbook and dispatch validation or publish commands to openclaw/releases-private.

Maintainer options:

  1. Align the sibling release runbook (recommended)
    Update the macOS validation, preflight, publish, and appcast references in .agents/skills/release-openclaw-maintainer/SKILL.md so they match the openclaw/releases path used by this PR and the current public workflow summary.
  2. Pause for release-owner confirmation
    If openclaw/releases-private is still intentionally valid for some maintainer-only macOS path, pause this PR until a release owner documents which commands belong to each repo.
Copy recommended automerge instruction
@clawsweeper automerge

Special instructions:
Update the macOS private validation/preflight/publish and release-readiness references in `.agents/skills/release-openclaw-maintainer/SKILL.md` so they use `openclaw/releases` where current workflows and this PR use `openclaw/releases`, then run `git diff --check` and `rg -n "releases-private|openclaw/releases|macos-release|public_release_branch" .agents/skills/release-openclaw-mac/SKILL.md .agents/skills/release-openclaw-maintainer/SKILL.md .github/workflows/macos-release.yml docs/reference/RELEASING.md`.

Next step before merge

  • [P2] A narrow docs repair can align the sibling release-maintainer skill with the mac skill and current public workflow without changing runtime or workflow code.

Security
Cleared: The diff is documentation-only and does not change workflows, permissions, dependencies, scripts, package resolution, secrets handling, or executable release logic.

Review findings

  • [P2] Update the sibling release runbook — .agents/skills/release-openclaw-mac/SKILL.md:85
Review details

Best possible solution:

Merge after .agents/skills/release-openclaw-maintainer/SKILL.md is aligned with the mac skill and current public workflow, or after a release owner documents an intentional repo split.

Do we have a high-confidence way to reproduce the issue?

Yes for the review finding: source inspection of the PR head shows the mac skill changed to openclaw/releases while the sibling release-maintainer skill still instructs the same macOS release flow to use openclaw/releases-private.

Is this the best way to solve the issue?

No, not yet; updating the mac skill is the right layer, but the maintainable fix needs the sibling release-maintainer runbook aligned in the same PR.

Full review comments:

  • [P2] Update the sibling release runbook — .agents/skills/release-openclaw-mac/SKILL.md:85
    This line moves the mac skill to openclaw/releases, but .agents/skills/release-openclaw-maintainer/SKILL.md still tells stable-release operators to run the same macOS validation, preflight, and publish paths in openclaw/releases-private. Landing only this file leaves contradictory release runbooks, so please align the sibling release-maintainer skill or document the intentional split before merge.
    Confidence: 0.92

Overall correctness: patch is incorrect
Overall confidence: 0.91

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against a82902c725b2.

Label changes

Label justifications:

  • P2: This is a normal-priority release-runbook correctness issue with limited blast radius but real operator impact.
  • merge-risk: 🚨 other: Green CI does not catch contradictory maintainer runbooks that can send release operators to the wrong release-ops workflow repo.
  • rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦞 diamond lobster and patch quality is 🦐 gold shrimp.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Sufficient (live_output): The PR body cites a real public macOS Release dispatch, and gh run view confirms run 28269425203 succeeded on release/2026.6.10; that proves the new public handoff command but not the sibling-doc drift.
  • proof: sufficient: Contributor real behavior proof is sufficient. The PR body cites a real public macOS Release dispatch, and gh run view confirms run 28269425203 succeeded on release/2026.6.10; that proves the new public handoff command but not the sibling-doc drift.
Evidence reviewed

PR surface:

Docs +41. Total +41 across 1 file.

View PR surface stats
Area Files Added Removed Net
Source 0 0 0 0
Tests 0 0 0 0
Docs 1 51 10 +41
Config 0 0 0 0
Generated 0 0 0 0
Other 0 0 0 0
Total 1 51 10 +41

Acceptance criteria:

  • [P1] git diff --check.
  • [P1] rg -n "releases-private|openclaw/releases|macos-release|public_release_branch" .agents/skills/release-openclaw-mac/SKILL.md .agents/skills/release-openclaw-maintainer/SKILL.md .github/workflows/macos-release.yml docs/reference/RELEASING.md.

What I checked:

Likely related people:

  • vincentkoc: Recent GitHub path history for the release-maintainer skill, public macOS workflow, and public releasing docs shows several June 2026 release-control and release-doc commits by Vincent Koc. (role: recent release workflow/docs contributor; confidence: high; commits: 09356fb9851e, abb6f04e0cac, f5a7f613ee4d; files: .agents/skills/release-openclaw-maintainer/SKILL.md, .github/workflows/macos-release.yml, docs/reference/RELEASING.md)
  • steipete: GitHub path history ties the mac release skill and public release-process documentation to release-skill routing and public evidence repo commits by Peter Steinberger. (role: release skill and public evidence repo contributor; confidence: high; commits: 23d38e4682dc, 4737e1905871, 910354b07f54; files: .agents/skills/release-openclaw-mac/SKILL.md, .github/workflows/macos-release.yml, docs/reference/RELEASING.md)
  • onutc: Merged PR history shows Onur Solmaz routed macOS publishing away from the public workflow and rewrote the release-maintainer guidance for the private/release-ops handoff path. (role: original macOS release handoff contributor; confidence: medium; commits: 8ed33c2aff24, 6e8d5cd5786b; files: .github/workflows/macos-release.yml, .agents/skills/openclaw-release-maintainer/SKILL.md)
What the crustacean ranks mean
  • 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
  • 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
  • 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
  • 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
  • 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
  • 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
  • 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works
  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

@clawsweeper clawsweeper Bot added proof: sufficient ClawSweeper judged the real behavior proof convincing. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. P2 Normal backlog priority with limited blast radius. merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. labels Jun 26, 2026
@RomneyDa
RomneyDa merged commit bdd365a into main Jun 26, 2026
36 checks passed
@RomneyDa
RomneyDa deleted the docs/macos-release-skill-ref branch June 26, 2026 23:08
@RomneyDa

Copy link
Copy Markdown
Member Author

@clawsweeper re-review

@clawsweeper

clawsweeper Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

🦞🧹
ClawSweeper could not start a re-review for this item.

Reason: re-review requires an open issue or PR.

wangmiao0668000666 pushed a commit to wangmiao0668000666/openclaw that referenced this pull request Jun 27, 2026
* docs: clarify macOS release workflow refs

* docs: clarify macOS release repo roles

* docs: document macOS release approval gate

* docs: align maintainer macOS release repo refs
github-actions Bot pushed a commit to Desicool/openclaw that referenced this pull request Jun 27, 2026
* docs: clarify macOS release workflow refs

* docs: clarify macOS release repo roles

* docs: document macOS release approval gate

* docs: align maintainer macOS release repo refs
xydigit-zt pushed a commit to xydigit-zt/xydigit-zt-openclaw that referenced this pull request Jun 28, 2026
* docs: clarify macOS release workflow refs

* docs: clarify macOS release repo roles

* docs: document macOS release approval gate

* docs: align maintainer macOS release repo refs
QiuYuang pushed a commit to QiuYuang/openclaw that referenced this pull request Jul 1, 2026
* docs: clarify macOS release workflow refs

* docs: clarify macOS release repo roles

* docs: document macOS release approval gate

* docs: align maintainer macOS release repo refs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintainer Maintainer-authored PR merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. P2 Normal backlog priority with limited blast radius. proof: sufficient ClawSweeper judged the real behavior proof convincing. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. size: S status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant