Retract v1.5.4 about nbio

[IceflowRE]

I've deleted the v1.5.4 when I publish v1.5.5, but users can still get v1.5.4 by some proxy because of their cache. Does retract work for that also?

You have deleted the GitHub release, go uses the git tags and the tag v1.5.4 exists and can/should also not be deleted.

When a module version is retracted, users will not upgrade to it automatically using go get, go mod tidy, or other commands. Builds that depend on retracted versions should continue to work, but users will be notified of retractions when they check for updates with go list -m -u or update a related module with go get.

Also

The comment may be shown by tools like go get and go list. It will be shown by gorelease and pkg.go.dev later on, too.

The commit looks good to me. But you might write it like Contains body length parsing bug. as it is shown to developer/end user.

[lesismal]

As the v1.5.4 has been deleted, can't do more except add this retract.

Updated the comment:
86e2b10

[IceflowRE]

As the v1.5.4 has been deleted, can't do more except add this retract.

Just to avoid confusion: The release was deleted, the tag still exists.

[lesismal]

Thanks for pointing it out!

I made a commit but I am not familiar with retract, is this correct?
a6684c2

I've deleted the v1.5.4 when I publish v1.5.5, but users can still get v1.5.4 by some proxy because of their cache. Does retract work for that also?

[IceflowRE]

Looks good.

[lesismal]

New skill +1, thanks a lot! 😄 ❤️