-
Notifications
You must be signed in to change notification settings - Fork 167
chore: release 1.27.0 #64
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
Conversation
1358f5e to
2e27edd
Compare
abf9f6d to
98684b8
Compare
73ea3ee to
4abeb1c
Compare
93aa42b to
f602252
Compare
6600bfc to
8df0b55
Compare
|
@IlyaFaer everything passed for your PR but are now failing for the release. Could you please take a look? |
|
@frankyn, taking a look |
|
@frankyn, yeah, I think, I got it. The same problem with I should do a separate fixing PR, ha? |
|
Yes please, this PR is autogenerated/updated whenever PRs are merged to master. Thanks for digging in @IlyaFaer |
e366c48 to
df560e1
Compare
|
The release build has started, the log can be viewed here. 🌻 |
|
🥚 You hatched a release! The release build finished successfully! 💜 |
* updated CHANGELOG.md [ci skip] * updated setup.cfg [ci skip] * updated setup.py [ci skip] Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
* updated CHANGELOG.md [ci skip] * updated setup.cfg [ci skip] * updated setup.py [ci skip] Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
🤖 I have created a release *beep* *boop*
1.27.0 (2020-04-01)
Features
Bug Fixes
This PR was generated with Release Please.