Skip to content

feat(templates): publish openclaw - #53

Open
CarmenDou wants to merge 1 commit into
mainfrom
feat/openclaw-undraft
Open

feat(templates): publish openclaw#53
CarmenDou wants to merge 1 commit into
mainfrom
feat/openclaw-undraft

Conversation

@CarmenDou

@CarmenDou CarmenDou commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

What

Publishes the openclaw template to the catalog: removes meta.draft: true and the README's draft note, and bumps 0.1.0 → 0.1.1 (with the image tag following) because the published 0.1.0 canonical tag must not be overwritten by the rebuild this change triggers — the image content itself is unchanged from #50.

How

  • insta.template.yaml: drop the draft flag; version: 0.1.1; image: …/openclaw:0.1.1.
  • README.md: drop the opening draft note (AGENTS.md only requires it while the template is draft).

Verify

  • Canonical 0.1.0 (same content as what 0.1.1 will rebuild) was smoke-tested on prod after feat(openclaw): make the draft template deployable on a wrapped official image #50 merged, on a fresh throwaway project (deleted): first deploy healthy, /startupz 200, Control UI origin seeded from the resolved service URL.
  • Full end-to-end (browser Control UI through origin → token → device pairing to a live dashboard) ran on the same content during feat(openclaw): make the draft template deployable on a wrapped official image #50.
  • cd templates && npm run lint passes with openclaw under the strict non-draft checks; npm run version-guard -- origin/main reports ✓ openclaw: 0.1.0 -> 0.1.1; the script test suite passes 66/66.
  • After merge: CI publishes openclaw:0.1.1 from main and the catalog entry goes live; a insta template deploy openclaw registry-path smoke follows as the final check.

🤖 Generated with Claude Code


Summary by cubic

Publishes the openclaw template by removing its draft flag and README draft note, and bumps 0.1.00.1.1 so the rebuild from this change doesn't overwrite the already-published canonical tag. Image content is unchanged from the smoke-tested build.

Verify

  • Canonical 0.1.0 passed a fresh-project smoke test on prod: healthy first deploy, /startupz 200, Control UI origin seeded.
  • Lint, the version guard, and the 66-test script suite all pass.
  • After merge, CI publishes openclaw:0.1.1 and the catalog entry goes live; a registry-path deploy smoke is the final check.

Written for commit baa71e8. Summary will update on new commits.

Review in cubic

Remove the draft flag and the README draft note: the wrapper image shipped with
#50, the canonical 0.1.0 was published from main and smoke-tested on a fresh
project (healthy first deploy, /startupz 200, explicit-origin seeding). Version
goes to 0.1.1 because the published 0.1.0 tag must not be overwritten by the
rebuild this change triggers; the image content is unchanged.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Re-trigger cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant