Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retract the accidentally-released v0.6.5. #194

Merged
merged 3 commits into from Nov 8, 2021
Merged

Conversation

creachadair
Copy link
Contributor

@creachadair creachadair commented Nov 5, 2021

Update the go.mod file to version 1.16, to allow the retract syntax.

Requires #195 (or equivalent) to be merged first.

In addition to this, I think we should move this release into a separate branch, revert the changes from master, and cut a v0.6.6 as a successor to v0.6.4 so that we can still have a viable mainline for bug fixes and such.

Update the go.mod file to version 1.16, to allow the retract syntax.
@@ -16,3 +16,6 @@ require (
go.etcd.io/bbolt v1.3.6
google.golang.org/grpc v1.38.0
)

// Breaking changes were released with the wrong tag (use v0.6.4).
retract v0.6.5
Copy link
Contributor

Choose a reason for hiding this comment

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

woah didnt know this was possible

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's a new feature with Go 1.16, but it is really helpful for cases like this. 🙂

@creachadair creachadair merged commit d3744d5 into master Nov 8, 2021
@creachadair creachadair deleted the mjf/retract-broken branch November 8, 2021 23:12
creachadair pushed a commit that referenced this pull request Nov 9, 2021
Update the go.mod file to version 1.16, to allow the retract syntax.
Mark v0.6.5 as retracted, since it contains large breaking package structure changes.
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.

None yet

2 participants