Closed Enselic closed 8 months ago
@trishume Friendly one-month ping. Collaborators can't access repo secrets, so you are the only one that can add one. Doing the steps above shouldn't take many minutes.
If you are uncomfortable with storing the secret on GitHub, I could make it a one-time masked input secret that is inputted each run, if you prefer. That way no secrets are stored anywhere.
But the risk of the secret leaking by GitHub is low (I have never heard of it happening), and if it happens it is not a super big deal, since it can't be used to remove us as owners from crates.io.
Closing in favor of https://github.com/trishume/syntect/pull/517 that does not require storing secrets on GitHub.
To make it easy to make releases (and we need a release to unblock https://github.com/sharkdp/bat/pull/2815), automate the process via GitHub Actions.
Create a workflow that:
I've been using a variant of this workflow for my own projects for quite a while now, and find that it works well.
New release process
After this lands, this will be the new release process:
Help needed to setup
Hi @trishume ! Would be great if you could help set up an automated release process. I only need your help with this:
Create a crates.io token
syntect
.If you prefer me to use a token belonging to my account, that's perfectly fine with me, just let me know. I'll then share it with you through gpg.
Create a GitHub Actions secret
crates.io
CARGO_REGISTRY_TOKEN
and paste the above tokenDone! Once that is done (which only you can do) I will release syntect 5.2.0 using the new process. I have confirmed that this process works with the changelog format of syntect by verifying with a toy project of mine.