release-1.0 branch now contains the set of commits we’re planning to call v1.0.1. You can view the list of commits here. As a patch release, this should be strictly non-breaking for existing code and should introduce no features, only bugfixes.
We invite users and especially package authors to test their code with a source build of the
release-1.0 branch to ensure that there are no changes in behavior aside from bugs being fixed. We plan to move forward with a 1.0.1 release after a few days, so let us know on GitHub by submitting an issue if you run into anything fishy. A package evaluation run showed no regressions in packages, so we’re likely all good here, but it’s always worthwhile to have more testing and assurance, especially for patch releases.