-
Notifications
You must be signed in to change notification settings - Fork 73
Add a CI to publish crates to crate.io #94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
I don't have crates.io access, I assume only niondir does. But it sounds like this would make it easier to get new versions published. I think regardless we need to start publishing new versions, the latest release is very very old. |
|
@schteve Yes, I think so. Can you contact him to do the setting on crate.io? It's pretty easy. |
|
@niondir Can you please do the setting on crate.io? It's pretty simple, only three fields need to be filled in (owner, name, workflow filename). |
|
should be active now |
|
@niondir Thanks a lot! Did you set up https://crates.io/crates/freertos-cargo-build as well? We also need it. |
|
Added as well |
|
I'm good with it, just so I understand, after merging this I can create new releases by pushing a tag starting with 'v'? Like 'v0.2.0'. |
#93