Once a tag is pushed to this repo, please consider it immutable. You have to control over the timeline of downstream usage. I've already bumped the Arch Linux package and sent it to the testing repository, now I see the last tag (1.85.0) was removed and re-tagged. Now I have to spend ten times as much time as it took to bump the package in the first place to handle the anomaly. First it breaks the "trust on first use" model, so I have to figure out if the release is even legit. Then I have to come up with a way to break the build systems cache to flush out the old source files, artificially bump the package version to get a rebuild that people can upgrade to, and so on.
If something goes wrong with the release process and there are post-release changes of any kind, just tag a new patch release and let everybody move forward normally please. Thanks.
Once a tag is pushed to this repo, please consider it immutable. You have to control over the timeline of downstream usage. I've already bumped the Arch Linux package and sent it to the testing repository, now I see the last tag (1.85.0) was removed and re-tagged. Now I have to spend ten times as much time as it took to bump the package in the first place to handle the anomaly. First it breaks the "trust on first use" model, so I have to figure out if the release is even legit. Then I have to come up with a way to break the build systems cache to flush out the old source files, artificially bump the package version to get a rebuild that people can upgrade to, and so on.
If something goes wrong with the release process and there are post-release changes of any kind, just tag a new patch release and let everybody move forward normally please. Thanks.