we should cut a tag for this after this is merged

H there,

I just noticed this was tagged as 0.0.2 even though there are breaking changes only available for Swift >= 5.7 (we are unable to build tag 0.0.2 on Xcode 13.4.1)

In looking at the README, this section:

The Swift Async Algorithms package has a goal of being source stable as soon as possible; version numbers will follow Semantic Versioning. Source breaking changes to public API can only land in a new major version.

Should we expect these breaking changes to continue to occur until the API reaches version 1.0.0? In other words should we be pinning this package to a fixed tag until 1.0.0 is released if we want to avoid breakages in our builds?

I'll answer my own question here, from https://semver.org/:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

Regardless, we may still want to revert the tag as we think about if we want 0.0.x to have this change or if it goes into 1.0. @phausler has been looking into it.