FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Release branch/tag collisions make source archives return HTTP 300 · Issue #2606 · zerotier/ZeroTierOne · GitHub

Release branch/tag collisions make source archives return HTTP 300 #2606

Description

Problem

The refs 1.16.1 and 1.16.2 each exist as both a release branch and a tag. GitHub cannot resolve the canonical source archive URLs unambiguously:

$ curl -sS -o /dev/null -w "%{http_code}\\n" https://github.com/zerotier/ZeroTierOne/archive/1.16.1.tar.gz
300
$ curl -sS -o /dev/null -w "%{http_code}\\n" https://github.com/zerotier/ZeroTierOne/archive/1.16.2.tar.gz
300

This breaks packaging and vendoring tools that use archive/<version>.tar.gz.

Explicit tag URLs work and redirect normally:

$ curl -sS -o /dev/null -w "%{http_code}\\n" https://github.com/zerotier/ZeroTierOne/archive/refs/tags/1.16.1.tar.gz
302
$ curl -sS -o /dev/null -w "%{http_code}\\n" https://github.com/zerotier/ZeroTierOne/archive/refs/tags/1.16.2.tar.gz
302

Requested cleanup

Please delete or rename the colliding 1.16.1 and 1.16.2 branch refs while preserving the release tags. Future release branches could use names such as release/1.16.2 to avoid colliding with tags.

The explicit archive/refs/tags/<version>.tar.gz form is a working consumer-side workaround.

Downstream tracking: eejd#2.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL