pb33f / openapi-changes

The world's sexiest OpenAPI breaking changes detector. Discover what changed between two OpenAPI specs, or a single spec over time. Supports OpenAPI 3.1, 3.0 and Swagger
https://pb33f.io/openapi-changes/
Other
180 stars 16 forks source link

Meta: Branches and tags collision in repository #163

Closed mguentner closed 1 week ago

mguentner commented 1 week ago

For some versions (now 0.0.68) there exists a tag and a branch with the same name. This breaks downloading source archives from GitHub for that rev:

https://github.com/pb33f/openapi-changes/archive/v0.0.68.tar.gz whereas https://github.com/pb33f/openapi-changes/archive/v0.0.67.tar.gz downloads the archive of the tag v0.0.67 just fine.

Background:

I packaged openapi-changes in nixpkgs. There are multiple tools, even bots available that automatically fetch the latest tags of a repository and update the attributes of the derivation accordingly. Since the fetcher fetches using a rev (which can be a tag or branch), the above demonstrated collision breaks this method and this means that one needs to specify the commit hash manually for this version of openapi-changes. :point_right: When there are no collisions (at least for new versions), we can use automation to get new openapi-changes asap into nixpkgs!

Possible solution: Delete the 0.0.68 branch if it is not needed :+1:

daveshanley commented 1 week ago

All old branches have been pruned. This should now be resolved.

mguentner commented 1 week ago

Thank you!