-
Notifications
You must be signed in to change notification settings - Fork 124
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
Prepare release 1.7.0 #369
Conversation
Yes I am still waiting for you in #345 (comment) and would like to include that in the release |
@niklasmohrin can you check your Matrix messages? |
@niklasmohrin sorry for bothering you again over this channel, but I sent you another message 🙂 |
Hmmmm, apparently I have something misconfigured over there 🤔 :D |
885e035
to
02e70a0
Compare
@@ -7,16 +7,13 @@ Run linting: | |||
Set variables: | |||
|
|||
$ export VERSION=X.Y.Z | |||
$ export GPG_KEY=EA456E8BAF0109429583EED83578F667F2F3A5FA | |||
$ export GPG_KEY=20EE002D778AE197EF7D0D2CB993FF98A90C9AB1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@niklasmohrin if you have a GPG signing key, you can replace this with your own key ID after the release.
@niklasmohrin I believe this is now ready. Could you check if everything looks good to you? Once that's done, I'll publish the release 🙂 |
Do we want to change the default features to |
Given that it's no urgent issue without workaround, and since it only affects people in networks that do active TLS interception, I think we can move that to the next release. |
Alright then, I will aim for the next release to be earlier than two years anyways :D |
@niklasmohrin rebased after merging the dependency updates! |
Did we forget anything?
Things that need to be done before the release:
...anything else?