Skip to content

fix: prevent upstream tags from polluting origin#165

Merged
anandgupta42 merged 1 commit intomainfrom
fix/prevent-upstream-tag-pollution
Mar 15, 2026
Merged

fix: prevent upstream tags from polluting origin#165
anandgupta42 merged 1 commit intomainfrom
fix/prevent-upstream-tag-pollution

Conversation

@anandgupta42
Copy link
Contributor

What does this PR do?

Prevents ~900 upstream OpenCode tags from leaking into our origin remote by scoping all git fetch and git push tag operations.

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Issue for this PR

Closes #164

How did you verify your code works?

  • Deleted 945 stale tags from both local and origin (952 → 7 remaining)
  • Verified all 6 changed files use explicit remote targeting and --no-tags where appropriate
  • Confirmed remaining tags are only Altimate releases: v0.1.0(-beta*), v0.2.0, v0.3.0, v0.3.1

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • New and existing unit tests pass locally with my changes

Changes across 6 files:

File Problem Fix
.github/workflows/ci.yml git fetch upstream auto-follows tags Added --no-tags
sdks/vscode/script/release git fetch --force --tags + git push --tags Explicit origin; push only new tag
github/script/release Same as above Same fix
script/publish.ts git push origin HEAD --tags Push only v${version}
RELEASING.md Docs use --tags Push only specific tag
script/upstream/README.md Docs use git fetch upstream --tags Changed to --no-tags

🤖 Generated with Claude Code

Multiple scripts and CI workflows were fetching/pushing tags in ways
that caused ~900 upstream OpenCode tags to leak into our origin remote:

- CI `git fetch upstream` auto-followed tags — added `--no-tags`
- Release scripts used `git push --tags` pushing ALL local tags to
  origin — changed to push only the specific new tag
- Release scripts used `git fetch --force --tags` without explicit
  remote — added explicit `origin`
- `script/publish.ts` used `--tags` flag — push only `v${version}`
- Docs referenced `git fetch upstream --tags` — fixed to `--no-tags`

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@anandgupta42 anandgupta42 merged commit 1eca6aa into main Mar 15, 2026
9 checks passed
anandgupta42 added a commit that referenced this pull request Mar 17, 2026
Multiple scripts and CI workflows were fetching/pushing tags in ways
that caused ~900 upstream OpenCode tags to leak into our origin remote:

- CI `git fetch upstream` auto-followed tags — added `--no-tags`
- Release scripts used `git push --tags` pushing ALL local tags to
  origin — changed to push only the specific new tag
- Release scripts used `git fetch --force --tags` without explicit
  remote — added explicit `origin`
- `script/publish.ts` used `--tags` flag — push only `v${version}`
- Docs referenced `git fetch upstream --tags` — fixed to `--no-tags`

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@anandgupta42 anandgupta42 deleted the fix/prevent-upstream-tag-pollution branch March 17, 2026 00:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upstream tags pollute origin remote

1 participant