Summary I recently needed to update a library to support building with Cabal 3.14.0.0. This was more difficult than I hoped. I think listing the exact (breaking) API changes in a single changelog document would have made it easier for me to do this. Should all major libraries adopt such a policy? I…

I think the CLC could very well publish a recommendation document for core libraries and their maintenance practices. But it should be clear that those are recommendations. We don’t want to overstep or dictate. It’s hard enough to find engaged maintainers.

I originally wanted to post this to the CLC issue tracker. But I thought there are people much more qualified to draw up such guidelines than me. So I would like to hear from you if you have any suggestions. Perhaps we can draft the guidelines together.

Also, one of the advantages of Cabal’s approach of linking to changelogs on github is that the changelogs can be revised without uploading a new package version. I think a better way to solve that is to allow changelog changes on Hackage via revisions or some similar mechanism that does not require …

I think that is a reasonable workflow. In practice, I tend to start at Step 2 and skip Step 1. My own interactions with the modern Cabal project suggest that it tries hard to encourage (and have) a comprehensive and useful change log, but things can slip through. It might be useful if the CONTRIBU…

I remember reading a thread/post that talked about tools for automated changelogs based on the library’s api, much like Elm. It would be nice if those tools were more prevalent in the ecosystem. Maybe even include their output in Changelog.md, or a new file.

Yeah, I think you mean this thread: [image] Maintain a golden test of your package's API with `diff-package-api` and `print-api` Announcements The machine never stops. Joining the publication of get-tested , I have the pleasure to welcome diff-package-api to t…

print-api has been lucky to receive more attention (and thus more tickets ) recently. The most important of them require work from people who understand the GHC API in some capacity, or are willing to learn just what’s required. I need help in that area, otherwise the developer experience will suffer…

What is the ideal dependency update workflow?

Learn

jaror September 29, 2025, 7:55am 7

Yeah, I think you mean this thread: