fix(ci): force the tag fetch in the deploy workflow - #8
Merged
Conversation
Every release tag pushed here fails to deploy, so the tag exists but ships no binaries. actions/checkout fetches the annotated tag, then the deploy step's 'git fetch --tags' refuses to touch the same ref: ! [rejected] v2026.08.07 -> v2026.08.07 (would clobber existing tag) The first deploy job to hit it exits 1 and fail-fast cancels every sibling, so no architecture uploads at all. This repo carries a vendored copy of _extension_deploy.yml that predates the fix. erpl-tunnel and anofox-tabfm already run 'git fetch --tags --force' and deploy cleanly; this copies their line across. Deleting and re-pushing the tag does not help -- verified on anofox-scenario. Also pins 'git tag --points-at HEAD' to its first match so EXT_VERSION cannot become multi-line.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every release tag pushed here fails to deploy — the tag exists but ships no binaries.
actions/checkoutfetches the annotated tag, then the deploy step'sgit fetch --tagsrefuses to touch the same ref:The first deploy job to hit it exits 1, and
fail-fastcancels every sibling — so no architecture uploads, not just the one that failed.Why this repo and not others
This repo carries a vendored copy of
_extension_deploy.ymlthat predates the fix. Across the fleet the split is exact:git fetch --tags --force(erpl-tunnel, anofox-tabfm)git fetch --tags(this repo, erpl, duckdb-gdrive, anofox-scenario, anofox-tabular)Deterministic, and ours to fix — not upstream's bug and not a race.
What does not work
Deleting and re-pushing the tag. Verified on anofox-scenario: identical failure. The tag was never the problem;
--forceis precisely the flag that lets fetch update a refactions/checkoutalready placed.Branched from
origin/maindeliberately — localmainhere has 9 unpushed commits that are not mine to push.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.