a side effect of creating a release pointed at a specific commit instead of a branch
The message should still exist, and will only appear if the target branch that’s selected when the release was created is master and the current state of the master branch in the repository has more commits than the release in question.
This release has it: https://github.com/tfiers/PkgGraph.jl/releases/tag/v0.1.0 ..but the other ones don't.
https://github.com/orgs/community/discussions/23890:
Hm, weird.