The v4.3.0 Release Notes and NEWS.md reference commits that were released in the v4.2.6 tag:
https://github.com/doorkeeper-gem/doorkeeper/compare/v4.2.5...v4.2.6
https://github.com/doorkeeper-gem/doorkeeper/blob/v4.3.0/NEWS.md
https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v4.3.0
They should be moved into the v4.2.6 release notes and NEWS heading appropriately.
Looks like @maclover7 forgot to move them from master under 4.2.6 release in time of publishing. And we just ignore it. Fixed for GH releases and NEWS.md, thanks!
Also added missed release for 4.2.6 (there was only tag)
Was 4.3.0 pushed to RubyGems? I'm still only seeing 4.2.6 there.
I think we need Tute to release the gem. Or give Nikita publishing rights.
On Thu, Feb 22, 2018, 5:33 PM Steven Harman notifications@github.com
wrote:
Was 4.3.0 actually pushed to RubyGems? I'm still only seeing 4.2.6 there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/doorkeeper-gem/doorkeeper/issues/1041#issuecomment-367845800,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtLwdRBycOfyirdeJ8ZPQF68IKaOBGIks5tXes9gaJpZM4SNsnn
.>
Justin Bull
PGP Fingerprint: E09D 38DE 8FB7 5745 2044 A0F4 1A2B DEAA 68FD B34C
@f3ndot Ah, OK. I'll reference master from my Gemfile for now. Thanks!
@stevenharman v4.3.0 now published to RubyGems
🤘
Most helpful comment
@stevenharman v4.3.0 now published to RubyGems