Retract version v0.10.0 #361
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
heanlan
approved these changes
Sep 5, 2024
The "target" of the v0.10.0 tag was "mutated" (the tag was created, then deleted, then created again with a different target commit). This should never be done for a Go module and can create issues for consumers of the module, as the original version will be cached in module proxies, and there will be a discrepancy between module proxies and the version control repository (this can lead to checksum mismatch issues). The best practice in that case seems to be to retract the invalid version, and release a new one (we will release v0.10.1 in our case). Signed-off-by: Antonin Bas <[email protected]>
antoninbas
force-pushed
the
retract-version-v0.10.0
branch
from
2b31d79 to
0a7ffcf
Compare
antoninbas
added a commit
to antoninbas/vmware-go-ipfix
that referenced
this pull request
Sep 5, 2024
The "target" of the v0.10.0 tag was "mutated" (the tag was created, then deleted, then created again with a different target commit). This should never be done for a Go module and can create issues for consumers of the module, as the original version will be cached in module proxies, and there will be a discrepancy between module proxies and the version control repository (this can lead to checksum mismatch issues). The best practice in that case seems to be to retract the invalid version, and release a new one (we will release v0.10.1 in our case). Signed-off-by: Antonin Bas <[email protected]>
antoninbas
added a commit
to antoninbas/vmware-go-ipfix
that referenced
this pull request
Sep 5, 2024
The "target" of the v0.10.0 tag was "mutated" (the tag was created, then deleted, then created again with a different target commit). This should never be done for a Go module and can create issues for consumers of the module, as the original version will be cached in module proxies, and there will be a discrepancy between module proxies and the version control repository (this can lead to checksum mismatch issues). The best practice in that case seems to be to retract the invalid version, and release a new one (we will release v0.10.1 in our case). Signed-off-by: Antonin Bas <[email protected]>
heanlan
pushed a commit
that referenced
this pull request
Sep 5, 2024
The "target" of the v0.10.0 tag was "mutated" (the tag was created, then deleted, then created again with a different target commit). This should never be done for a Go module and can create issues for consumers of the module, as the original version will be cached in module proxies, and there will be a discrepancy between module proxies and the version control repository (this can lead to checksum mismatch issues). The best practice in that case seems to be to retract the invalid version, and release a new one (we will release v0.10.1 in our case). Signed-off-by: Antonin Bas <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The "target" of the v0.10.0 tag was "mutated" (the tag was created, then deleted, then created again with a different target commit). This should never be done for a Go module and can create issues for consumers of the module, as the original version will be cached in module proxies, and there will be a discrepancy between module proxies and the version control repository (this can lead to checksum mismatch issues).
The best practice in that case seems to be to retract the invalid version, and release a new one (we will release v0.10.1 in our case).