Generally, I do not commit Manifest.toml, docs/Manifest.toml and test/Manifest.toml (where applicable) to git repositories for packages.
However, as a result, sometimes these become out of date for local clones of packages repos. I can of course always update them manually, but I am wondering if there is a semi-automated solution that would at least give a warning about them being outdated whenever I activate any of these projects.
(Bonus question: should docs/ and test/ projects ] dev ..?)
in my Project.toml files for both docs/ and test/. This makes docs CI simpler (no need to add the package) and works as long as you build your docs on 1.11. It doesn’t matter for ] test MainPackage so CI tests work also for older juila versions. It is very convenient for cases where you ] activate MainPackage/test (which is the environment I have activated 99% of the time when developing MainPackage).
This doesn’t exactly warn about outdated manifests, or even remove the need for “manual” updating, but I would recommend that all projects include a Makefile for dev-tasks.
I use make distclean to remove all Manifest.toml files in the project:
I’m in the habit of typing make distclean on a somewhat regular basis, e.g., after switching between non-trivial branches or before making releases.