Skip to content

apparmor: retract v0.2.3 - #51

Open
thaJeztah wants to merge 1 commit into
moby:mainfrom
thaJeztah:retract_023
Open

thaJeztah wants to merge 1 commit into
moby:mainfrom
thaJeztah:retract_023

Conversation

@thaJeztah

Copy link
Copy Markdown
Member

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.

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>

@vvoland vvoland left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@thaJeztah

Copy link
Copy Markdown
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants