The scenario that created this question:
We have a package that is a dependency of another package, sometimes making changes to the \"parent\" package causes the d
In addition to Thomas Jones-Low's answer, if you only modify the package BODY, a dependent object might not be marked as invalid.
However, as soon as you modify the package specification, that is bound to happen.