This was not intentional, but fallout from two things:

1. A quirk in the way the Flutter CLI tool calculates the version on the `master` channel (it only looks at version tags that are on direct ancestors); and
2. The fact that the last beta release was not based on a dev release.

To fix this, I will update the flutter conductor release tool to always tag the branch point when publishing a new release branch.