I'm going to be publishing the 0.1.0 tag of the warg crates to crates.io; thanks to Alex, I have the secret incantations required to set up the CI to auto-publish the crates on new tags, so in the future when we create a tag on the repo, it'll build and publish the crates for us automatically
nice
i think it's probably time to remove the "demo" from the repo (and related "run" command) too
I still use those for all my tests...but sure it doesn't need to be in the repo
or at the very least update it to not use core modules
@Lann Martin @Kyle Brown are either of you administrators on bytecodealliance/registry
? if so, can you bump my privs to whatever role is allowed to define CI secrets?
Yep one sec
OK should be good now; let me know when you're done
ok all done, added a secret for an API access token for crates.io
ok i'm going to recreate the v0.1.0 tag and see if things work :fingers_crossed:
:nervous: https://github.com/bytecodealliance/registry/actions/runs/6331611075/job/17196520098
looks like the secret wasn't set up correct, fixing
@Lann Martin can i get access to the repo again to modify the secret?
done
I'll just switch it back tomorrow; i'm only keeping it relatively locked down on principle
Ok, I think I figured out the token issue, but I screwed up on squatting warg-api
, accidentally added a 0.1.0 dummy release, which I immediately yanked; contacted the crates.io folks to see if there's anyway to purge it given it has 0 downloads and no source.
if they're not able to, I may have to have warg-api
at 0.1.1 and the rest at 0.1.0 for the first release (my bad)
auto-publish worked! we now have published 0.1.0 (except for warg-api
, which is 0.1.1) packages on crates.io
@Lann Martin feel free to make me a pleb again
I think putting it out as 0.1.1
won't be a problem given we're about to go to 0.2
anyway
if it's more effort to grab exactly 0.1.0
, I wouldn't worry too much about it
i ended up publishing just that crate as 0.1.1
indeed, figured not a big deal if we're about to do a 0.2.0
Last updated: Nov 22 2024 at 16:03 UTC