update to latest slack-api-ref#169
Conversation
| @@ -1,5 +1,6 @@ | |||
| ### 0.9.2 (Next) | |||
|
|
|||
| * [#169](https://github.com/slack-ruby/slack-ruby-client/pull/169): Updated to latest slack-api-ref; adds [Conversations API](https://api.slack.com/docs/conversations-api) and support for locale; **removes `groups_close`** - [@jmanian](https://github.com/jmanian). | |||
There was a problem hiding this comment.
We usually just call these things as separate line items, no need to bold anything.
So
[#169](https://github.com/slack-ruby/slack-ruby-client/pull/169): Added [Conversations API](https://api.slack.com/docs/conversations-api) - [@jmanian](https://github.com/jmanian).
[#169](https://github.com/slack-ruby/slack-ruby-client/pull/169): Removed `groups_close` - [@jmanian](https://github.com/jmanian).
| g.long_desc %( Gets information about a channel. ) | ||
| g.command 'info' do |c| | ||
| c.flag 'channel', desc: 'Channel to get info on.' | ||
| c.flag 'include_locale', desc: 'Set this to true to receive the locale for this channel. Defaults to false.' |
There was a problem hiding this comment.
This is new, so needs a changelog line too, eg. "Added include_locale option to channels_info, rm_start, ..."
There was a problem hiding this comment.
Yep, it's hidden in the middle of that one long changelog item I wrote 😉 . I'll split it up into 3 items.
|
This will need to bump version to 0.10.0 indeed. Want to help out and make the next release @jmanian? If yes, what's your rubygems email? |
|
Sure, I'll give it a shot. Does this give you what you need https://rubygems.org/profiles/jmanian |
|
Sent you an invite and added to Rubygems, assigning #170 to you. Please follow https://github.com/slack-ruby/slack-ruby-client/blob/master/RELEASING.md |
|
Oh, did you want me to do the 0.10.0 bump as part of this PR? |
|
You can do that part of the release, no need to PR. |
2 participants
There's a potentially breaking change in here, which is that they seem to have removed
groups.close. I'm not sure if there's a special way to call that out on the changelog (I bolded it), or if that has implications for versioning (0.10?).