The release infrastructure for DBX Ruby (e.g. rake candidate:release) does not currently automate the creation of a new stable branch when the minor version changes. This adds a bit more friction to the release of new minor (and major) versions, and shouldn't be hard to automate.

The other part of a minor/major release is updating the relevant evergreen projects, so they reference the correct prior versions. I don't know if that configuration change can be modified or not, but it's worth investigating.