As we've had a lot of work go in since 0.15.0, including some features like interruption (which projects like Krustlet would really like to experiment with), do we think it's time to cut a 0.16.0 release?
sounds good to me! Are there any pending PRs we should wait for, or are we good to go?
I personally don't see any that we would need to wait for, but wouldn't hurt to wait for others to respond before releasing
0.16 is now up!
We're finally getting to the point where the script mostly runs to completion on its own, so cutting releases is much less of a hassle than it used to be
So if there are any PRs out there that should be released, we can just do another release
thanks, Dan!
holy cow that was a fast turnaround
nice on all the scripts and such working!
It looks like the update PR had the publish step skipped, no tags created.
@Dan Gohman btw for publishing, one thing I do for wasm-bindgen is I don't have a sleep but I also publish with --no-verify
with --no-verify
it means that it'll only fail publication of binaries or packages with examples
if the index isn't updated yet
and to publish I run the script and ignore all cargo publish
failures
only one fails typically for wasm-bindgen (the CLI which has a binary), and then I come back later and rerun the script
so one thing we can probably do is publish with --no-verify
, run publication for everything, then sleep, then rerun the whole script if anything failed
or maybe automating that would be hard but that's the idea
it's fine to publish the same thing twice b/c crates.io will just reject it
Last updated: Dec 23 2024 at 13:07 UTC