-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.6.11 release is missing binary assets #219
Comments
As a temporary workaround, installation of v1.6.10 can be used
|
Sure, but that'd require me changing my CI. Not worth it for what's probably a temporary problem. |
@ThiefMaster @insolor We deleted v1.6.11 since there is a problem with the release that we are looking into. v1.6.10 is now the latest. |
This reverts commit 27b9a19. The upstream release was deleted, see transifex/cli#219 (comment)
The problem is resolved: https://github.com/transifex/cli/releases/tag/v1.6.11 I've already reverted pinned tx v1.6.10 version in workflows in my repos, everything works fine. |
Please don't re-tag releases. If there was a problem with a release just bump the patch version and re-release when you get it fixed. Re-using the same Git tags and version numbers causes all sorts of trouble downstream. If a release is actively dangerous you can delete the tag, but just an incomplete release process should not result it a tag deletion and re-posting of the same tag. This already went out and got packaged downstream by package systems that don't rely on binary assets, then the sources went away with the tag, and now they are back with the same tag and different checksums and it's just a mess. Bumping the patch version is much cleaner for downstream workflows. |
https://github.com/transifex/cli/releases/tag/v1.6.11
This is breaking the curl-pipe-bash installation:
The text was updated successfully, but these errors were encountered: