9point6, 1 year ago

Big releases are harder to test and debug issues.

If your release contains a single change and something goes wrong, you’ve got a pretty good idea of where the problem is before you even start to look.

If the friction of creating a release is low (with automated tooling) and updating is (typically) automatic there’s not really a good reason to not release as often as possible in most cases.