We notice that minor changes to

pants.toml

invalidates lots of build caches. There are sections of

pants.toml

that we would expect to change more regularly (e.g. cli aliases). Are there any thoughts about how to separate/shield from that?

Can you demonstrate in an example repo? I would expect

pants.toml

changes to only invalidate things that depend on the specific section that was changed. But I also wouldn't be surprised to find that it's more eager than it needs to be...

pants.toml

will cause

pantsd

to restart (which will clear memoization), but should not invalidate any persistent caches