chore(ci): adopt .runtime-version push-mode cascade signal #3
Ghost
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "chore/runtime-version-file"
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?
Summary
Consumer side of the push-mode cascade pivot from molecule-core#20.
.runtime-version(currently0.1.129) at repo root.publish-image.ymlnow reads it via aresolve-versionjob 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-compatinputs.runtime_version— manualworkflow_dispatch.runtime-versionfile — push-mode cascade (new)''— Dockerfilerequirements.txtdefaultSequencing
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: pushrebuilds against the OLD requirements.txt floor.Test plan
workflow_dispatchwith explicitruntime_versioninput still routes correctly (untested — code-review only; the chain is precedence-ordered)Refs molecule-core#14, molecule-core#20.
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: 1. client_payload.runtime_version (forward-compat with future GitHub-style dispatch if Gitea ever adds it) 2. inputs.runtime_version (manual workflow_dispatch override) 3. .runtime-version file (push-mode cascade — the new path) 4. '' (Dockerfile requirements.txt default) No behavioural change for PRs / manual dispatches; only fills in the on-push case where previously the version was empty. Sequencing context: this PR (and 8 sibling PRs to the other template repos) MUST land before molecule-core#20 v2 is merged — otherwise the first cascade push would trigger an on-push rebuild that pins the OLD requirements.txt floor instead of the freshly-published version. Refs molecule-core#14, molecule-core#20, molecule-core/issues/20.Phase 3 push-mode cascade (.runtime-version + 2-job resolve→publish pattern). Independent review.