Stream: git-wasmtime

Topic: wasmtime / issue #3422 Automate more of Wasmtime's releas...


view this post on Zulip Wasmtime GitHub notifications bot (Oct 06 2021 at 20:13):

alexcrichton commented on issue #3422:

I'll note that while I've tested these workflows for automatically creating PRs I have not tested the one that publishes to crates.io. I'm hoping we can give it a spin on the first release, and if things go wrong we can always run the command manually. I suspect it'll take a release or two to get the invocations precisely correct.

Before merging this we'll need to configure two separate secrets in CI. One is a GitHub personal access token and one is a crates.io publication token. My plan here is to create a wasmtime-publish (or similar) bot account which we'll have tokens for and will be part of the wasmtime-publish team on crates.io. Once this PR gets approved I'll work on making that bot account.

view this post on Zulip Wasmtime GitHub notifications bot (Oct 26 2021 at 14:17):

alexcrichton commented on issue #3422:

@sunfishcode would you be ok reviewing this? I can tag others as well if you're busy

view this post on Zulip Wasmtime GitHub notifications bot (Oct 26 2021 at 14:20):

sunfishcode commented on issue #3422:

Yeah, I can review this.

view this post on Zulip Wasmtime GitHub notifications bot (Oct 26 2021 at 15:25):

alexcrichton commented on issue #3422:

Ok I've set up the bot account @wasmtime-publish and I've given it write access to this repository as well as adding it to the wasmtime-publish team on crates.io. New crates should get published via that bot account and the personal access token is installed to allow it to push to the repo and make PRs and such.

I think that means that this is all set and ready to go, so I'm going to merge. We can talk about a new version this Thursday and give this release process a spin (not 1.0, just the next version)


Last updated: Nov 22 2024 at 17:03 UTC