release-rome-image
Skill904 starsChanged 5 days agoMITView on GitHub
Release a new Rome runtime image by pushing a `vX.Y.Z` tag — pick the version, verify main is releasable, push the tag, and confirm the image published to Docker Hub. Covers the `v*` runtime-image tag only, not the desktop app (`desktop-v*`) and not npm packages (`ui-v*`, `app-runtime-v*`).
- Commits and pushes
In this repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- ios/CLAUDE.mdCLAUDE.md
- rome_apps/CLAUDE.mdCLAUDE.md
- add-oauth-integrationSkill
- babysit-prSkill
- color-auditSkill
- dddSkill
- file-issueSkill
- imports-ofSkill
- loop-northstarSkill
- loop-reconcileSkill
- move-codeSkill
- respond-to-reviewSkill
- secondary-text-auditSkill
- todos-to-github-projectSkill
- ux-semantics-auditSkill
- validate-oauth-integrationSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Read the commit that the tag will point at.
- Distinctive: line 44
Read the current stable tags.
- Distinctive: line 67
Create and push the tag, which starts the publish.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release a new Rome image
A pushed vX.Y.Z tag is the release. .github/workflows/docker-publish.yml builds the multi-arch image and publishes it to yunfanye/rome, with no approval gate between the push and Docker Hub. Get explicit confirmation before the push. Verify the published image after it.
The tagging contract covering the semver gate, tag immutability, and latest movement lives in docs/releases.md.
Out of scope
- Desktop releases use the
desktop-v*tag and a separate pipeline. - npm package releases belong to release-please. Never create those tags by hand.
1. Preflight
The tag lands on origin/main, and docker-publish.yml runs no CI gate of its own.
Read the commit that the tag will point at.
git fetch origin --tags && git rev-parse origin/mainList the recent CI runs.
gh run list --branch main --workflow CI --limit 5- Find the run for the exact commit from step 1 and confirm the status is
success. CI cancels superseded runs, so a rapid series of merges leavescancelledruns on real commits. If the run failed, was cancelled, or is still running, stop and report it. Confirm no release is already in flight.
gh run list --workflow "Docker Hub Publish" --limit 3
2. Pick the version
Read the current stable tags.
git tag --list 'v[0-9]*' | sort -V | tail -5- For a patch release, use the helper in step 3. The helper computes the next patch version.
- For a minor or major release, take the version from the user.
- For a prerelease, use
vX.Y.Z-rc.N. A prerelease publishes its own docker tag and never moveslatest.
Two constraints decide the number. A published version is immutable, so re-pushing a released version fails and the fix for a bad release is the next version up. latest moves only when the new version is the highest stable version in the registry.
3. Cut the tag
For a patch release:
Print the planned tag and target commit.
scripts/dev/create-patch-release-tag.sh --dry-run- Show that output to the user and wait for an explicit yes.
Create and push the tag, which starts the publish.
scripts/dev/create-patch-release-tag.sh
The user can also click Run workflow on main in the Actions tab instead. That run allocates the same next patch version and checks CI itself.
For a minor, major, or prerelease version, the helper does not apply, because it bumps the patch version only. Confirm the version with the user, then tag origin/main directly.
git tag -a v1.1.0 origin/main -m "Release v1.1.0" && git push origin refs/tags/v1.1.04. Verify the publish
Watch the run to completion.
gh run watch "$(gh run list --workflow "Docker Hub Publish" --limit 1 --json databaseId --jq '.[0].databaseId')"Confirm the version reached the registry.
curl -fsSL "https://hub.docker.com/v2/repositories/yunfanye/rome/tags?page_size=20" | jq -r '.results[].name'- Report the published version, whether
latestmoved, and the build SHA. A running instance reports the baked version at/api/build-info.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

