unkin/rpmbuilder
3
0
Fork 0
Code Issues 9 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

Track claude-code versions via update-gh using GitHub tags #163

New Issue
Open
opened 2026-05-17 11:34:10 +10:00 by unkinben · 0 comments
unkinben commented 2026-05-17 11:34:10 +10:00
Owner
Copy Link
Copy Source

Summary

claude-code has no GitHub Releases — versions are tracked via Git tags at
https://github.com/anthropics/claude-code. The binary is downloaded from the
internal artifact proxy (not from GitHub), so the upgrade path is different from
other packages.

Required changes

  1. Version detection — use the GitHub tags API
    (GET /repos/anthropics/claude-code/tags) instead of the releases endpoint.
    Add a github_version_source: tags field (or similar) to metadata.yaml to
    opt into this mode.

  2. Download URL — the build script already fetches from
    artifactapi.k8s.syd1.au.unkin.net/api/v1/remote/claude-ai/claude-code-releases/${PACKAGE_VERSION}/linux-x64/claude.
    No change needed there; update-gh only needs to write the new version into
    metadata.yaml.

  3. Tag normalisation — claude-code tags are plain semver (2.1.126), no
    v prefix. Ensure the version parser handles both forms.

Acceptance criteria

  • ./tools/build upgrade claude-code detects the latest tag and updates
    rpms/claude-code/metadata.yaml with the new version
  • Existing download URL in build.sh continues to work unchanged
## Summary `claude-code` has no GitHub Releases — versions are tracked via Git tags at https://github.com/anthropics/claude-code. The binary is downloaded from the internal artifact proxy (not from GitHub), so the upgrade path is different from other packages. ## Required changes 1. **Version detection** — use the GitHub tags API (`GET /repos/anthropics/claude-code/tags`) instead of the releases endpoint. Add a `github_version_source: tags` field (or similar) to metadata.yaml to opt into this mode. 2. **Download URL** — the build script already fetches from `artifactapi.k8s.syd1.au.unkin.net/api/v1/remote/claude-ai/claude-code-releases/${PACKAGE_VERSION}/linux-x64/claude`. No change needed there; update-gh only needs to write the new version into metadata.yaml. 3. **Tag normalisation** — claude-code tags are plain semver (`2.1.126`), no `v` prefix. Ensure the version parser handles both forms. ## Acceptance criteria - `./tools/build upgrade claude-code` detects the latest tag and updates `rpms/claude-code/metadata.yaml` with the new version - Existing download URL in `build.sh` continues to work unchanged
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
benvin (BenVincent) droneci unkinben (Ben Vincent)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/rpmbuilder#163
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?