chore(ci): adopt .runtime-version push-mode cascade signal #2

claude-ceo-assistant · 2026-05-07T10:08:20Z

claude-ceo-assistant commented

2026-05-07 10:08:20 +00:00

Summary

Consumer side of the push-mode cascade pivot from molecule-core#20.

Adds .runtime-version at repo root.
publish-image.yml now reads it via a resolve-version job and forwards the value to the reusable build workflow as a third-priority source.

See molecule-core#20 issuecomment-923 for the full Phase 2 design.

Resolution chain

client_payload.runtime_version — legacy/forward-compat
inputs.runtime_version — manual workflow_dispatch
.runtime-version file — push-mode cascade (new)
'' — Dockerfile requirements.txt default

Sequencing

This PR (and 8 siblings on the other workspace-template repos) must land before molecule-core#20 v2 merges — otherwise the first cascade push fires on: push rebuilds against the OLD requirements.txt floor.

Refs molecule-core#14, molecule-core#20.

## Summary Consumer side of the push-mode cascade pivot from molecule-core#20. - Adds `.runtime-version` at repo root. - `publish-image.yml` now reads it via a `resolve-version` job and forwards the value to the reusable build workflow as a third-priority source. See molecule-core#20 issuecomment-923 for the full Phase 2 design. ## Resolution chain 1. `client_payload.runtime_version` — legacy/forward-compat 2. `inputs.runtime_version` — manual `workflow_dispatch` 3. `.runtime-version` file — push-mode cascade (new) 4. `''` — Dockerfile `requirements.txt` default ## Sequencing This PR (and 8 siblings on the other workspace-template repos) must land **before** molecule-core#20 v2 merges — otherwise the first cascade push fires `on: push` rebuilds against the OLD requirements.txt floor. Refs molecule-core#14, molecule-core#20.

claude-ceo-assistant added 1 commit 2026-05-07 10:08:20 +00:00

chore(ci): adopt .runtime-version push-mode cascade signal

CI / validate (pull_request) Successful in 10m40s

Details

CI / validate (push) Successful in 10m37s

Details

4989682e20

Background: post-2026-05-06 SCM is Gitea, not GitHub. Gitea 1.22.6 has
no repository_dispatch / workflow_dispatch trigger API (empirically
verified across 6 candidate paths in molecule-core#20 issuecomment-913).
The molecule-core/publish-runtime.yml cascade therefore cannot fire
templates via curl-dispatch — pivots to push-mode instead.

This PR is the consumer side of that pivot:

- .runtime-version file at repo root — single line, plain version
  string. Currently 0.1.129 (latest published as of 2026-05-07).
  publish-runtime overwrites this on each cascade.

- publish-image.yml gains a resolve-version job that reads the file
  and forwards the value to the reusable build workflow as the
  third-priority source in the resolution chain.

Sequencing context: this PR (and 8 sibling PRs to the other template
repos) MUST land before molecule-core#20 v2 is merged.

Refs molecule-core#14, molecule-core#20.

Ghost approved these changes 2026-05-07 10:12:46 +00:00

Ghost left a comment

First-time contributor

Phase 3 push-mode cascade (.runtime-version + 2-job resolve→publish pattern). Independent review.

claude-ceo-assistant merged commit 55b060413c into main

2026-05-07 10:12:47 +00:00

claude-ceo-assistant referenced this issue from a commit

2026-05-07 10:12:48 +00:00

Merge pull request 'chore(ci): adopt .runtime-version push-mode cascade signal' (#2) from chore/runtime-version-file into main

Sign in to join this conversation.

No reviewers

No Label

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-ai-workspace-template-autogen#2