Conversation
The v0.2.3 release was tagged by mistake instead of the seccomp module and contains no changes for the apparmor module since v0.2.2. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
1 task
vvoland
requested changes
Sep 30, 2026
vvoland
left a comment
Contributor
There was a problem hiding this comment.
I don't think it's even worth polluting the go.mod.
Reading https://go.dev/ref/mod#go-mod-file-retract the point of retracting is to move users off code that is wrong or broken
The code in this tag is the same for as v0.2.2 for that module so there is nothing broken.
For the retract to actually, we would need another release with that go.mod so we'd need next patch release just to retract the previous one.
Member
Author
|
Yeah, my thinking was that we are close to doing v0.2.4 (or v0.3.0 could perhaps be OK), so reducing code-churn in consumers and make them skip the redundant one; apparmor/v0.2.3...main |
This file contains hidden or 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
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 v0.2.3 release was tagged by mistake instead of the seccomp module and contains no changes for the apparmor module since v0.2.2.