trending/paperclip
1
0
Fork 0
mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-02 02:07:25 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
018993140f42f9afa7bba5fee05fddaa9e7dfa9d
paperclip/doc/RELEASE-CHECKLIST.md
T
Devin FoleyandPaperclip 8ee8f1fd6e ci: retire recurring public cloud image builds (#13827) 
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work.
> - Core publishes standard images and source verification for
downstream services.
> - Managed services can now compose private images from the signed
standard image.
> - Core still builds a second public cloud image on every master push
and release.
> - That duplicate producer consumes build capacity and retains an
obsolete readiness contract.
> - This pull request retires recurring cloud publication while
preserving the standard producer and rollback artifacts.

## Linked Issues or Issue Description

Refs #13797 and #13789. Related: #12856 changes image dependency
packaging; it does not retire this producer.

**What existing behavior does this improve?**

Core's recurring Docker publication and Cloud readiness workflow.

**Current behavior**

Master pushes call the legacy cloud publisher from Cloud readiness.
Release tags and manual Docker runs call it too. Canary promotion also
requires the legacy image.

**Proposed behavior**

Publish standard Core images and retain `Cloud source verified v1`. Let
downstream services build their managed image. Keep explicit commit
previews and existing images available.

## What Changed

- Remove `docker-cloud.yml`, its master and release callers, and its
unused cache selector.
- Remove the legacy image/migrator wait and `Cloud deployable v1` job.
Keep the full source verification workflow and exact source-proof name.
- Make canary promotion inspect and promote the standard image only.
- Preserve signed standard-image publication, direct migrator
publication, and explicit `release.yml` previews. The preview path still
uses the Dockerfile `cloud` target.
- Update workflow, preview, build-stamp, and packaging tests. Exercise
the promotion shell with mocked registry commands, including
missing-image and missing-tag cases.
- Document frozen legacy aliases, consumer requirements, preview
compatibility, and rollback retention.

## Verification

- All 377 workflow tests pass: `node --test
.github/scripts/tests/*.test.mjs`.
- All 129 release-registry tests pass: `pnpm test:release-registry`.
- Focused source-proof, standard-image, preview, and workflow tests
pass: 256 tests.
- Focused image packaging/build-stamp tests pass: 16 tests.
- Actionlint passes on all three changed workflow files. `git diff
--check` passes.
- Full local `pnpm build` and `pnpm -r typecheck` pass.
- The policy follow-up updates an old assertion that required the
removed readiness job. All 37 source-proof/release-workflow tests pass
locally.
- Full local `pnpm test:run` did not complete successfully while the Mac
ran out of disk space. No full-suite pass is claimed. Removed 1.2 GiB of
generated Cargo output from this isolated worktree with `cargo clean`.
GitHub CI passed on the final head: 52 successful checks and 2 optional
skips.
- Fresh Greptile review for `4f5fe1951f0bd7f7739cf6655d395ff78f1ed944`:
**5/5**, successful current-head check, zero review threads.
- September 23 refresh: the unchanged PR head merges cleanly with
current master `db8f8fe5b73a2697684a30261b0d306a9c631aba`. In an
isolated temporary worktree, all 377 workflow tests and 29
release/preview tests pass on the combined tree. `git diff --cached
--check` passes.
- Refreshed Actionlint workflow validation passes with ShellCheck
disabled. Full Actionlint reports the same 10 existing ShellCheck
diagnostics as master, with no added diagnostics. No source changes or
new PR commits were needed.
- The full local build/typecheck and current-head Linux CI results above
remain the verification for the unchanged PR head. They were not rerun
for this metadata-only refresh. No image publication or tenant
deployment was initiated for this refresh.

## Risks

**Deployment prerequisite satisfied (September 23):** The combined
cleanup release is deployed to staging and production, and production
Support is verified. Active managed-fleet automation uses standard-image
composition. Explicit immutable previews remain supported by the
retained preview publisher. This PR is ready for maintainer review; keep
auto-merge disabled and wait for explicit merge authorization.

- A consumer still selecting `Cloud deployable v1` will stop advancing
at the last legacy-ready commit. Confirm active automatic consumers use
the standard-image composition contract before merge.
- Legacy cloud release-channel aliases stop advancing. Standard
self-hosted aliases continue.
- This PR deletes no registry images, cache tags, migrators,
credentials, or runner infrastructure. Existing immutable releases
remain usable for rollback.
- Explicit legacy previews remain for commit-specific operator
deployments. Retiring that compatibility path requires a separate
consumer migration.
- These changes affect CI publication, not database schema or
application behavior.

## Model Used

OpenAI Codex, GPT-6. The runtime does not expose a more specific model
identifier or context-window size. Used repository inspection,
reasoning, code editing, shell tools, and test execution.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

---------

Co-authored-by: Paperclip <noreply@paperclip.ing>
2026-09-23 19:35:19 -07:00

3.8 KiB
Raw Blame History

Release Checklist

The release captain's checklist for every lane. The mechanics live in RELEASING.md; the user-facing channel guide is CHANNELS.md.

Canary (automatic, every master push)

  • the push's Release run is green (verify + publish)
  • npm view paperclipai@canary version matches the expected canary
  • Docker :canary updated (the same push's Docker run)
  • a canary publish failure is a release-infra regression — fix it before trusting later promotions

Nightly (automatic, 09:00 UTC)

  • the scheduled run selected the newest green canary, or skipped with a job-summary reason (no new candidate / already shipped / red smoke)
  • the release smoke suite passed against the exact candidate canary before anything published
  • npm view paperclipai@nightly version shows the new -nightly.N
  • nightly/v* tag pushed; :nightly image built
  • on a tag-push rejection (workflows-permission error), follow the recovery commands in the job summary

To force a nightly: dispatch release.yml with channel: nightly (optional exact canary in source_version; dry_run to preview).

Beta (manual promotion)

Happy path:

  • pick the nightly to promote (empty source_version selects the newest)
  • dispatch release.yml with channel: beta
  • approve the npm-beta environment gate
  • npm view paperclipai@beta version shows the new -beta.N
  • beta/v* tag pushed; :beta image built
  • post-publish smoke (smoke_beta) is green
  • draft_stable_notes pushed release-notes/v<beta-version>; open the notes PR from the job-summary link
  • during the soak: edit the notes PR into release voice and merge it (the stable promotion reads releases/beta/v<beta-version>.md from master)

Fix path (cherry-picked candidate):

  • cut candidate/beta-<target> from the chosen nightly's source commit
  • cherry-pick only the required fixes; push the branch
  • dispatch channel: beta with candidate_branch
  • confirm the job summary records the cherry-picked commits and that full verification ran on the candidate head
  • after shipping: reconcile the fixes to master, delete the branch

Stable (manual promotion)

  • pick the beta to promote; its source commit is source_ref
  • the beta has soaked ≥ 3 days with no open beta-blocker issues
  • the beta's notes PR (releases/beta/v<beta-version>.md) is merged on master — preflight fails, before the approval gate, without it
  • dispatch release.yml with channel: stable (a dry run first shows the resolved version and soak state without publishing)
  • approve the npm-stable environment gate
  • npm view paperclipai version (dist-tag latest) shows the stable
  • vYYYY.MDD.P tag pushed; GitHub Release created; :latest and the versioned Docker tags built
  • if the soak gate was bypassed, skip_soak_justification carries a real written reason (it lands in the job summary)
  • open and merge the canonicalization PR (release-notes/v<version>-canonicalize) so the notes land at releases/vYYYY.MDD.P.md

Fix path: candidate/release-<target> from the beta's source commit; the soak gate will demand a justification because the exact bits were not soaked — write one that stands on its own. A candidate branch carries its own releases/vYYYY.MDD.P.md (preflight prefers source-tree notes), so author the notes as a commit on the candidate.

After any incomplete run

The failure playbooks in RELEASING.md cover: red canary, skipped or failed nightly, a beta that looks bad during soak, partial stable releases, broken latest, and rejected tag pushes. Every publish job's summary names what completed and what remains.

Reference in New Issue View Git Blame Copy Permalink