@xenorange/yarn-patch-package-update-squash

TL;DR: Add as dev dependency, then run yarn patch-update-squash <package>

Similar to yarn patch --update <package>, but does not create a patch of patches. Based on this discussion:

https://github.com/yarnpkg/berry/issues/3851

In effect, this script behaves like the proposed yarn patch --update --squash <package>.

Usage

Install via

yarn add --save-dev @xenorange/yarn-patch-package-update-squash

Then, instead of yarn patch --update <package>, just run

yarn patch-update-squash <package>

And proceed as you would with yarn patch. See also yarn's doc on package patching.

Release

Check CHANGELOG.md and package.json for the version. Then:

yarn npm publish --access public
git tag -a x.y.z
git push origin x.y.z

Then create a github release and set version to next snapshot.