Repository navigation
Tags
Tags
Stamp one build id for the whole release run The first tag publish since the marker system landed failed the publish cross-check: on a tag push inputs.build_id is empty, so each package script fell back to its own packaging minute and the three haas-build.json markers disagreed (gpu vs cpu). A tiny stamp job now emits one UTC yyyyMMdd-HHmm build value that all three build jobs share whenever the caller did not supply a build id. GPT review noted run ids would order lexicographically across digit-count changes in haas-upgrade; the shared timestamp keeps the established format and ordering.