Add release Github actions

[jindongjie]

Could we publish this HAL library to crates.io? I see placeholders, but the crate is empty. GitHub something is hard to access in some country—I suffer for this issue this morning :(

[jindongjie]

By the way,having per‑MCU templates would help a lot,right now I need copy-paste through examples and READMEs to get the project settings and dependencies correct.

[romainreignier]

By the way,having per‑MCU templates would help a lot,right now I need copy-paste through examples and READMEs to get the project settings and dependencies correct.

There is ch32-hal-template already.

[jindongjie]

@romainreignier Thanks！

[Codetector1374]

I think we need @andelf 's help for that. He owns the cargo publishing permission.

[aq1018]

@andelf

Do you want to add a github action to automate the release process for ch32-hal? I think same treatment could apply to ch32-metapac / qingke. A regular release cadence would be nice. I can draft some PRs and see if you like how it works. Let me know!

[andelf]

@aq1018 Sounds great to me. Feel free to draft some PRs.

[kpcyrd]

To clarify, you are looking for a pull request that uses Github actions to publish to crates.io when a tag is pushed to this repository, correct? :)

[jindongjie]

To clarify, you are looking for a pull request that uses Github actions to publish to crates.io when a tag is pushed to this repository, correct? :)

correct，If there is a github pull request merged or other important change to the repo should hook the github action and let it auto push the repo to crate.io.

[andelf]

Quick update: ch32-metapac 0.1.0 has been published to crates.io now: https://crates.io/crates/ch32-metapac/0.1.0

The release automation discussion here still makes sense for future ch32-hal / ch32-metapac releases.