---
name: release-peekaboo
description: "Prepare, publish and verify Peekaboo through its hosted GitHub Actions release workflow."
metadata: { "clawdbot": { "emoji": "👁️", "requires": { "bins": [ "pnpm", "gh", "git", "node", "npm" ] } } }
title: release-peekaboo
canonical_url: https://skilld.dev/gh/openclaw/peekaboo/release-peekaboo
last_updated: 2026-10-15T08:39:19.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install openclaw/peekaboo/release-peekaboo`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/release-peekaboo`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/openclaw/peekaboo/release-peekaboo) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/release-peekaboo`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/release-peekaboo --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/release-peekaboo --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Peekaboo Release

Read [docs/RELEASING.md](../../../docs/RELEASING.md) first; it is the source of
truth. Follow repo `AGENTS.md`. Only `.github/workflows/release.yml` publishes
`openclaw/Peekaboo` and `@steipete/peekaboo`. Never release or publish without an
explicit release command; a rehearsal does not authorize publication.

1. Prepare a PR with consistent version surfaces and dated root/CLI changelog
   sections, validated by the existing release preflight. Hosted Actions extracts
   notes from `CHANGELOG.md`; no separate notes file or local publisher is used.
   Merge the preparation PR and wait for green **push CI on that exact commit**.
2. Rehearse from main with
   `gh workflow run release.yml --ref main -f version=X.Y.Z -F dry_run=true`.
   Review the frozen source and artifacts, approve the `release` environment,
   and verify the run succeeds without publication.
3. With explicit publication authorization, create and push an annotated
   SSH-signed `vX.Y.Z` tag on the same verified commit, using the canonical release
   SSH key accepted by `.github/release-allowed-signers`. Resolve that key through
   the private credential guidance if needed; never copy private key material
   into the repo. Approve the publication run's `release` environment gate.
   Tag pushes also trigger other workflows; the release CI gate fails while
   checks are still running. Wait for them to succeed, then rerun failed release
   jobs as needed. Never replace a published tag or rebuild an existing version.
4. Verify GitHub Release assets and `checksums.txt`, and compare the published
   notes to the root changelog. Check npm's exact version, dist-tag, tarball,
   integrity and publish time; compare the downloaded registry tarball's SHA-512
   integrity with the exact tarball from the hosted run. Run published CLI proof
   with `npm exec` from `/tmp` so the checkout cannot shadow the package.
5. Verify the Homebrew tap formula's version, URLs and checksums. Review and merge
   the Actions-created appcast closeout PR, then verify the feed on main and the
   post-release `Unreleased` section. Report the release/run/closeout links and
   any incomplete handoff. Retry hosted handoffs only after checking what is
   already published; do not overwrite an existing version.

Signing/notarization credentials stay in the hosted `release` environment; npm
uses OIDC. Local terminal/fleet notarization helpers are qualification tools and
are not an alternate publication path.
