-
Notifications
You must be signed in to change notification settings - Fork 207
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
chore: release 2.7.0 #452
chore: release 2.7.0 #452
Conversation
111b6de
to
30fbf7a
Compare
30fbf7a
to
9c08a09
Compare
9c08a09
to
8ab6ab2
Compare
8ab6ab2
to
f8097b3
Compare
Hi @anguillanneuf is it alright for me to release this? I'd like to get the self-signed JWT and expanded range for |
@busunkim96 I think it's okay to release. @plamut Sound ok to you? |
This commit removed the coverage requirement from Release notes are a bit weird, they also contain the following, for example:
As a precaution, we should at least double check what's actually contained in the release plus groom the release notes accordingly. |
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.
@busunkim96 @anguillanneuf Took another look, plenty of autogenerated stuff, but seems good.
I also see why several entries refer to the same commit, it's simply because that commit was so large.
Please have a look at the suggested changes in CHANGELOG, but otherwise I think we can release this today.
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.
Thank you @plamut! I see the large commit you mean.
The release build has started, the log can be viewed here. 🌻 |
🥚 You hatched a release! The release build finished successfully! 💜 |
Thanks @plamut! |
🤖 I have created a release *beep* *boop*
2.7.0 (2021-07-24)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.