Yes, that’s sufficient. If you don’t use TagBot, they don’t go anywhere unfortunately, and it might make sense to be pretty minimal with it (e.g. just “some changes are breaking”) to not waste your time. However, I would be interested in some mechanism to make this information available somewhere.
- The simplest place would be to add it to the registry itself, since we have the information available at registration time. But that would be a bad idea, as it would bloat the registry: everyone would need to download release notes for every package regardless of whether or not they use it.
- We could do something else with the information at registration time. I suppose there could be some secondary system with other metadata that could be queried. This could be a lot of work and maintenance so I think it’s a bad idea too.
- Or, and I think this is likely the best option, there could be some standard place to put release notes in the package itself, and we could modify the automerge rule to skip requiring release-notes-via-registrator if they are present in this other place. This would likely lead to tons of bikeshedding about the format and location, but it would have the advantage that by sitting next to the code, it would get shipped with the package code itself only when necessary by the existing distribution mechanisms (Pkg.jl + PkgServers) and could be queried locally (maybe there could be
pkg> changelog MyPkgto see the latest changes).