Description
🤖 Generated with Claude Code in an interactive session with the maintainer.
Evidence
Codex found both of these on #243, and both are the same in devantler-tech/actions today:
publish-app.yamlpushes the version, SHA andlatestimage tags before it checks thatdeploy-pathholds a well-formeddeployment.yamlwith exactly one matching container. A bad manifest therefore fails the release after GHCR has changed, andlatestcan point at an image with no deployable manifest.publish-app.yamlandpublish-manifests.yamlaccept any tag that merely starts with a semantic version, such asv1.2.3garbage, and publish it as1.2.3garbage. Flux's semver selection and Docker's semver metadata do not treat that as the intended release.
Acceptance criteria
- Every manifest and container check runs before any registry write, and the digest is still injected after the build.
- Both workflows accept only a complete semantic-version tag (with optional pre-release and build metadata) and refuse anything else before publishing.
- Tests cover a bad manifest (nothing pushed) and a malformed tag (refused).
Rough size: S.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Effort
None yet
Projects
- StatusShow more project fields✅ Done
Activity
chore: agent-claim #263 nonce=f61bb105bd450226afc80488985258b5