Skip to content

Strip release-process narration from per-repo docs #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thedavidmeister merged 1 commit into from
Aug 20, 2026
Merged

Strip release-process narration from per-repo docs #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 1 addition & 8 deletions .github/workflows/package-release.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,5 @@
name: Package Release
# Deploy repo: a manual `sol-v*` tag is the sole release trigger.
# rainix-autopublish's merge-driven, next-version lifecycle is wrong for this
# shape: it bumps the release version on every merge, while the frozen deploy
# tag only advances at deploy time.
#
# The on-chain deploy is separate and manual, run BEFORE tagging; this never
# broadcasts. rainix-tag-release's chain verification is the intended gate: a
# release is declared here only once it is a deployment that already happened.
# Deploy repo: released by a manual `sol-v*` tag via rainix-tag-release.
on:
push:
tags:
Expand Down
7 changes: 2 additions & 5 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,8 +76,5 @@ Mutation and coverage campaigns: see `.claude/rules/mutation-profile.md`.

Deployed via the Zoltu deployer, so the address is a pure function of the
bytecode. A deploy is a human-dispatched run of `Manual sol artifacts`, never a
merge, and comes BEFORE the tag. Releases are manual `sol-v*` tags:
`package-release.yaml` runs `rainix-tag-release`, which cuts the frozen
`src/generated/<tag>/` record via `script/Build.sol --sig "cutRelease()"` and
publishes `rain-extrospection-deploy` to Soldeer. `releasedSuites()` is empty
until the first release is cut. See README.md.
merge, and comes BEFORE the tag. Releases are manual `sol-v*` tags;
`releasedSuites()` is empty until the first release is cut. See README.md.
9 changes: 2 additions & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,13 +44,8 @@ that needs a network.

## Releases

Releases are manual `sol-v*` tags, never merges. `package-release.yaml` runs
`rainix-tag-release`, whose `snapshot-generate-cmd` runs
`script/Build.sol --sig "cutRelease()"`: it regenerates the rolling candidate,
freezes it as `src/generated/<tag>/`, regenerates the released-suites libs from
the record that now holds the release, verifies the live chains against the
fresh pins, publishes `rain-extrospection-deploy` to Soldeer and commits the
frozen record back to `main`.
Releases are manual `sol-v*` tags, never merges. Tagging runs
`rainix-tag-release`, which never broadcasts; its mechanics live in rainix.

The on-chain deploy is separate and human-dispatched, run BEFORE tagging: the
`Manual sol artifacts` workflow runs `script/Deploy.sol` for the `extrospect`
Expand Down
Loading