molecule-ai/molecule-core
52
0
Fork 2
Code Issues 183 Pull Requests 14 Actions 2 Packages Projects Releases Wiki Activity

Template workflow migration sweep — 4 templates still on suspended pipeline #1186

New Issue
Open
opened 2026-05-15 12:54:31 +00:00 by hongming · 0 comments
hongming commented 2026-05-15 12:54:31 +00:00
Owner
Copy Link
Copy Source

Problem

Only openclaw and hermes workspace templates have successfully migrated to the post-2026-05-06 pipeline. Other templates either:

  • Have no ECR image (google-adk, smolagents, amazon-strands — ECR repo doesn't exist)
  • Have an ECR repo but no :latest tag (deepagents — publish-image never fired since suspension)

Per-template state (2026-05-15)

Template Main green? ECR repo? :latest? Notes
openclaw ✓ ✓ ✓ Live, runtime 0.1.1000
hermes ✓ ✓ ✓ Live, runtime 0.1.1000
deepagents ✓ ✓ ✗ .gitea/workflows/ missing; publish-image still on .github/workflows/
google-adk ? ✗ ✗ Never built post-suspension
smolagents ? ✗ ✗ Never built post-suspension
amazon-strands ? ✗ ✗ Never built post-suspension

Root cause for deepagents

.github/workflows/publish-image.yml has multiple Gitea-1.22.6-hostile shapes (each empirically verified to fail on this Gitea version):

  1. repository_dispatch trigger (Gitea 1.22.6 REST endpoint NYI; post-suspension cascade uses push-of-.runtime-version, not repository_dispatch).
  2. workflow_dispatch.inputs (Gitea silently parses and rejects per feedback_gitea_workflow_dispatch_inputs_unsupported).
  3. Workflow lives in .github/ not .gitea/. Some repos read .github/ as fallback, but template/runtime publish chain expects .gitea/.
  4. Targets ghcr.io (suspended) not ECR.
  5. Uses unpinned actions/checkout@v4 (Gitea action resolution prefers pinned SHA refs).

Recommended migration plan

Apply the openclaw/hermes migration pattern to each remaining template:

  1. Create .gitea/workflows/publish-image.yml inlining the ECR push (no cross-repo uses:)
  2. Trigger on push: branches: [main] (drop repository_dispatch, drop workflow_dispatch.inputs)
  3. Drop cache-from: type=gha + cache-to: type=gha,mode=max (broken in act_runner DinD per [internal#1182]) — or use type=registry if cache perf matters
  4. Drop the Boot smoke step (broken in act_runner DinD per [internal#1181])
  5. Pass smoke env vars to the import smoke step (per [internal#1180])
  6. Delete .github/workflows/publish-image.yml after Gitea version reads .gitea/ correctly
  7. Bump .runtime-version to 0.1.1000 to trigger the first publish

Acceptance criteria

  • All 6 templates have a fresh ECR image
  • All publish workflows live under .gitea/workflows/
  • Runtime cascade (publish-runtime.yml → push .runtime-version → publish-image.yml) works end-to-end

Workspace test coverage

Without ECR images, users cannot select these templates from the canvas when creating new workspaces (or selection fails at boot). This is user-facing.

Related

## Problem Only `openclaw` and `hermes` workspace templates have successfully migrated to the post-2026-05-06 pipeline. Other templates either: - Have no ECR image (`google-adk`, `smolagents`, `amazon-strands` — ECR repo doesn't exist) - Have an ECR repo but no `:latest` tag (`deepagents` — publish-image never fired since suspension) ## Per-template state (2026-05-15) | Template | Main green? | ECR repo? | :latest? | Notes | |----------|-------------|-----------|----------|-------| | openclaw | ✓ | ✓ | ✓ | Live, runtime 0.1.1000 | | hermes | ✓ | ✓ | ✓ | Live, runtime 0.1.1000 | | deepagents | ✓ | ✓ | ✗ | `.gitea/workflows/` missing; publish-image still on `.github/workflows/` | | google-adk | ? | ✗ | ✗ | Never built post-suspension | | smolagents | ? | ✗ | ✗ | Never built post-suspension | | amazon-strands | ? | ✗ | ✗ | Never built post-suspension | ## Root cause for deepagents `.github/workflows/publish-image.yml` has multiple Gitea-1.22.6-hostile shapes (each empirically verified to fail on this Gitea version): 1. `repository_dispatch` trigger (Gitea 1.22.6 REST endpoint NYI; post-suspension cascade uses push-of-.runtime-version, not repository_dispatch). 2. `workflow_dispatch.inputs` (Gitea silently parses and rejects per `feedback_gitea_workflow_dispatch_inputs_unsupported`). 3. Workflow lives in `.github/` not `.gitea/`. Some repos read `.github/` as fallback, but template/runtime publish chain expects `.gitea/`. 4. Targets `ghcr.io` (suspended) not ECR. 5. Uses unpinned `actions/checkout@v4` (Gitea action resolution prefers pinned SHA refs). ## Recommended migration plan Apply the openclaw/hermes migration pattern to each remaining template: 1. Create `.gitea/workflows/publish-image.yml` inlining the ECR push (no cross-repo `uses:`) 2. Trigger on `push: branches: [main]` (drop `repository_dispatch`, drop `workflow_dispatch.inputs`) 3. Drop `cache-from: type=gha` + `cache-to: type=gha,mode=max` (broken in act_runner DinD per [internal#1182]) — or use `type=registry` if cache perf matters 4. Drop the Boot smoke step (broken in act_runner DinD per [internal#1181]) 5. Pass smoke env vars to the import smoke step (per [internal#1180]) 6. Delete `.github/workflows/publish-image.yml` after Gitea version reads `.gitea/` correctly 7. Bump `.runtime-version` to 0.1.1000 to trigger the first publish ## Acceptance criteria - All 6 templates have a fresh ECR image - All publish workflows live under `.gitea/workflows/` - Runtime cascade (publish-runtime.yml → push .runtime-version → publish-image.yml) works end-to-end ## Workspace test coverage Without ECR images, users cannot select these templates from the canvas when creating new workspaces (or selection fails at boot). This is user-facing. ## Related - openclaw migration PRs: #5, #6, #7, #8, #9 - hermes migration PRs: #17, #18, #19, #20 - Follow-up cache + smoke issues: molecule-core#1180, #1181, #1182 - Sweep mandate: `feedback_post_suspension_migration_must_sweep_dormant_repos`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
approved
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 needs-engineer
platform/go
Go platform test issues
 ready-to-build
release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1186
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?