Greptile Summary

Switches the release workflow trigger from release: published to push: tags so Docker multi-platform builds start immediately when a semver tag is pushed, allowing maintainers to verify the image before the GitHub Release is published and avoiding duplicate watcher notifications from repeated re-publishes.

• The include pattern [0-9]*.[0-9]*.[0-9]* digit-anchors each segment, so cloud-build tags like cl-1.9.5 cannot match (they start with c, not a digit); the !cl-* exclusion adds a redundant but harmless explicit guard.
• The docker/metadata-action step already reads the version from github.ref (the git tag), so it produces identical Docker tags whether the event is a tag push or a release publish — no downstream tag changes needed.

Confidence Score: 5/5

Safe to merge — the change is a minimal, well-scoped trigger swap that does not alter any build, push, or deployment logic.

The only change is the workflow trigger: release: published becomes push: tags with a digit-anchored pattern. The rest of the job — Docker login, metadata extraction, multi-platform build, and push — is untouched. The new pattern correctly excludes cloud-build tags and aligns with the existing publish.yml convention. No build logic, credentials handling, or downstream steps are affected.

No files require special attention.

Important Files Changed

_{Reviews (2): Last reviewed commit: "chore: restrict tag trigger to digit-bas..." | Re-trigger Greptile}