Skip to content

feat: try alternate v-prefix variant when fetching tags#15

Merged
critesjosh merged 1 commit intomainfrom
feat/resilient-tag-v-prefix
Mar 30, 2026
Merged

feat: try alternate v-prefix variant when fetching tags#15
critesjosh merged 1 commit intomainfrom
feat/resilient-tag-v-prefix

Conversation

@critesjosh
Copy link
Copy Markdown
Collaborator

Summary

  • When fetching a git tag fails, automatically retries with the alternate v-prefix variant ("v1.0.0""1.0.0") so versions can be specified with or without the v prefix
  • Makes needsReclone v-prefix-insensitive so a repo checked out at v1.0.0 won't trigger a re-clone when the config says 1.0.0 (and vice versa)
  • Adds 4 new tests covering both fallback directions and the needsReclone comparison

Test plan

  • All 183 tests pass (npm test)
  • Manual: sync with a version like 4.2.0-aztecnr-rc.2 (no v) against a repo that tags with v prefix
  • Manual: sync with a version like v4.0.0-devnet.2-patch.1 against a repo that tags without v prefix

🤖 Generated with Claude Code

Some repos use tags without the "v" prefix (e.g. "4.2.0-aztecnr-rc.2")
while others use it (e.g. "v4.0.0-devnet.2-patch.1"). When fetching a
tag fails, automatically retry with the alternate v-prefix variant
(add "v" if missing, strip "v" if present). Also makes needsReclone
v-prefix-insensitive so mismatched prefixes don't trigger unnecessary
re-clones.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@critesjosh critesjosh merged commit 9d99007 into main Mar 30, 2026
6 checks passed
@github-actions
Copy link
Copy Markdown

🎉 This PR is included in version 1.16.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant