[Question] About release v6.4.8 #578
Comments
|
@rkoster the release @chenrui333 I couldn't follow on the second part. What do you mean the "commit got re-tagged from the latest release..."? |
|
v6.4.8 has been published, thanks @chenrui333 for bringing this up. Not really sure what to do about the checksum mismatch. Could you maybe describe the solution you are seeing for the case where the re-tagging has already happened? Or is this more a heads up to not re-tagg going forward? |
rkoster
moved this from Inbox
to Pending Review | Discussion
in Foundational Infrastructure Working Group
|
Hi. I'm also a homebrew maintainer. Ideally you should not retag, if possible. Some projects use "x.y.z.RC" tags, or "alpha/beta" tags. You could also mark it as "pre-release" in GitHub too; with should trigger a warning on our side. You can close here as the situation has been mitigated. |
|
Re-tags should be avoided where possible. Where avoiding them isn't possible, the re-tag should be made as conspicuous as possible. See the Git docs for more in this; it actually has some rather strong words about re-tagging. |
See: cloudfoundry/bosh-cli#578 Closes #90669. Signed-off-by: rui <rui@chenrui.dev> Signed-off-by: BrewTestBot <1589480+BrewTestBot@users.noreply.github.com>
|
Closing issue since it has been mitigated on the homebrew side of things |
👋 Just to check if the v6.4.8 is intended to be the latest release. If so, it would be better to mark the release as
latest release. Thanks!Also, it looks like the commit got re-tagged from the latest release which caused the checksum mismatch for go 1.17.3 update on the homebrew side.
The text was updated successfully, but these errors were encountered: