Diego Rodrigues de Sa e Souza d5b03504c8 fix(ci): re-point Docker :latest tag on release (#5301) (#5311) ...

On a `release: released` event the freshly-created git tag is often not yet
visible to `git fetch --tags` when docker-publish runs, so the :latest-promotion
gate built its candidate set purely from `git tag -l` and resolved the highest
semver to the previous version — leaving :latest one release behind.

Extract the decision into scripts/ci/should-promote-latest.sh, which folds the
current VERSION into the candidate set before picking the highest stable semver,
making promotion independent of tag-sync timing. A patch published after a higher
minor still won't grab :latest.

Regression guard: tests/unit/build/should-promote-latest-5301.test.ts (spawns the
real helper with fixture tag lists; proves the race case now promotes).

2026-06-29 05:35:56 -03:00

..

should-promote-latest.sh

fix(ci): re-point Docker :latest tag on release (#5301) (#5311)

2026-06-29 05:35:56 -03:00