Have the changes in the git tag and/or the release on GitHub?

[dorianmarie]

What do you think?

I was trying to know what changed between 5.20.0 and 5.21.1

I think this will also get picked up by dependabot

[dorianmarie]

Oh I see there is a https://github.com/minitest/minitest/blob/master/History.rdoc also

[stefannibrasil]

Oh, thanks for the History link! Yeah, I was confused why dependabot PR did not contain any release notes. I remember it had at some point?

[zenspider]

If you go to tags and click on a version you're interested in, there is a compare dropdown that lets you pick another version and generates urls like so:

v5.20.0...v5.21.1

[zenspider]

https://rubygems.org/gems/minitest also has "Review Changes"

https://my.diffend.io/gems/minitest/5.20.0/5.21.1

[stefannibrasil]

Thanks, @zenspider ! I'm still not sure why, for example, dependabot used to pick up the changelog/commits in the version:

faker-ruby/faker#2804

but on the latest PR, it did not have any of the commit changes: faker-ruby/faker#2888

Maybe this is a bug on dependabot and not here? It's not a big deal, though, just trying to understand :)

[zenspider]

Dunno. Try filing a bug on it and see what they come up with.

[stefannibrasil]

That's usually what I do, I was just trying to confirm nothing had changed here before doing that ;) Thank you for your patience and for maintaining the gem 😊

[zenspider]

Please refer to this ticket there or link to that ticket here.

[dorianmarie]

I think putting what's in History.rdoc into the git tags would help, it's much easier to review than reviewing source code diff

(In My Humble Opinion)

Closing this as that's not really a bug, more a For Your Information

[stefannibrasil]

Please refer to this ticket there or link to that ticket here.

Sorry, got busy with other things! I was about to do that when I noticed that dependabot opened a PR correctly this time:

faker-ruby/faker#2894 🤷‍♀️

I can see the version changes by clicking on the "compare view" link. I think this was just a glitch because all the other PRs have been opened with the details. I will keep an eye out if it happens again. If it does, I will open the bug report.