don't release a new package version if the only change is devDep updates

[trentm]

Would it be possible to have the release-please release automatic not bother with a new release for a particular package if the only change in that package has been to its devDeps?

For example, if you look at #2211, most of the new package versions there are because there was a change in the contrib-test-utils devDep. IMHO that's not worth a new release of a package. The result is unnecessary churn.

[JamieDanielson]

I can go either way here. I wonder if there is a way we can specify certain packages to be exempt. Some dependencies like TypeScript can have an impact on released versions. At least major TypeScript versions, with some config changes and/or generated types files.

Although I guess we don't have to release yet either - this will accumulate changes if we leave it open right? So maybe it's just a note to hold off on merging the PR for release until we feel there's enough reason to publish a new release.

[trentm]

Some dependencies like TypeScript can have an impact on released versions.

Touché