Check for cabal file update?

[pbrisbin]

I've been bitten a few times by making a maintenance change (like version bounds) and not having a stack build --file-watch running at the time. This means nothing updates .cabal in response to my package.yaml changes. Since CI will fix .cabal itself and be Green, this mistake can go all the way to main and end up failing way later (on release).

Should stack-action actively check for this? In other words, if it finds a dirty .cabal after building, it could fail the test.

[pbrisbin]

Same for stack.yaml.lock.