-
Notifications
You must be signed in to change notification settings - Fork 215
chore: release 1.3.0 #27
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
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.
Just a comment on the wording.
Optional: Fix release notes from the previous release? (dead issue links, wording)
|
||
### Features | ||
|
||
* **pubsub:** ordering keys ([#26](https://www.github.com/googleapis/python-pubsub/issues/26)) ([cc3093a](https://www.github.com/googleapis/python-pubsub/commit/cc3093a2c0304259bc374bc2eeec9630e4a11a5e)) |
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.
The **pubsub:**
prefix is redundant here, and release notes should contain full sentences (AFAIK).
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.
I talked to Ben (who made the bot) and he says it just comes from the "pubsub" part of "feat(pubsub)". The part between the parens just provides extra context. We can omit it unless we want to standardize on a few contextual tags: tests, system-tests, gapic, publish-path, subscribe-path, etc. Just a thought.
I'm going to merge the PR and then send a follow-up to clean up these unnecessary "pubsub" tags.
General question - is a human supposed to change any stuff that might not be desired in the PR, or is the bot's version final, and the release notes format used here is the new norm? |
As per meeting notes - ordering keys should not be released just yet, as there is still some pending work remaining. |
63c006c
to
1feaa24
Compare
5e1b107
to
b58d0d8
Compare
The release build has started, the log can be viewed here. 🌻 |
🥚 You hatched a release! The release build finished successfully! 💜 |
🤖 I have created a release *beep* *boop*
1.3.0 (2020-02-20)
Features
This PR was generated with Release Please.