Would you consider tagging v0.11.0? #2342

Hi! I'm working on the ConanCenter package for stdexec (conan-io/conan-center-index#30060), and I wanted to ask whether you'd consider tagging a release. It would help us a lot.

Since #2116, both CMakeLists.txt and meson.build declare 0.11.0, but there's no tag for it yet. The existing tags (nvhpc-*, gtc-2026) aren't version numbers, so each package manager ends up making one up. vcpkg ships version-date: 2026-05-25, and ConanCenter would have to publish 0.0.0.cci.<date>. Each one points at a different commit, which makes it hard for users to know which stdexec version they actually have.

Would it be possible to tag v0.11.0? If it could happen after #2341 is merged, even better. The tagged sources could then be configured and installed without network access, and ConanCenter could package that tag directly without patches.

For future releases, whatever cadence works best for you is fine by us. Even tagging alongside the nvhpc-* snapshots would already be great, as long as the version in CMakeLists.txt and meson.build gets bumped first.

Thanks a lot for considering it, and for all the work on stdexec!