-
Notifications
You must be signed in to change notification settings - Fork 649
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
Plan to release bbolt 1.4.0 #553
Comments
Rough plan:
|
Quick question: is it possible to use the bbolt 1.4.0 release before the actual release without building myself? Just tried this command with no luck: # v1.4.0 Not found
go install go.etcd.io/bbolt/cmd/[email protected]
go: go.etcd.io/bbolt/cmd/[email protected]: go.etcd.io/bbolt/cmd/[email protected]: invalid version: unknown revision 1.4.0
Edit: It seems that this command does exactly this, downloading bbolt latest master branch, although version command says it is version 1.3.7, which does make sense. # seem to download 1.3.7 but bbolt version command seem to work,
C:\portainer>go install go.etcd.io/bbolt/cmd/bbolt@master
go: downloading go.etcd.io/bbolt v1.3.7-0.20231025151518-d094cd712c9a
C:\portainer>bbolt version
bbolt Version: 1.3.7
Go Version: go1.21.3
Go OS/Arch: windows/amd64 |
I am planning to create tag |
Tag v1.4.0-alpha.0 was just created. |
Planning to release v1.4.0-alpha.1 Please read #745 to get all the changes since 1.4.0-alpha.0 |
Tag v1.4.0-alpha.1 was created. |
Tag v1.4.0-beta.0 was just created. |
Some notable changes in bbolt 1.4.0:
internal/common
;Please see the complete changes to be included in 1.4.0 in milestone 1.4.0.
Note that etcd 3.6.0 will depend on bbolt 1.4.0. Previously I mentioned that etcd 3.6.0 will depend on bbolt 1.3.8, it is a typo. I already updated the ticket #542, sorry for the confusion. etcd 3.4 and 3.5 will continue to depend on bbolt 1.3.x.
We need to cut branch
release-1.4
, based on which the bbolt 1.4.0 will be released. Afterwards, it only accepts bug fixes, and any feature changes will only be merged into the master branch.@mitake @ptabor @serathius @spzala @wenjiaswe @tjungblu @cenkalti @fuweid @jmhbnz
The text was updated successfully, but these errors were encountered: