[PR #211] [MERGED] Use Github Action to automatically publish crate to crate.io #316

New issue

Closed

opened 2026-02-27 20:24:14 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 20:24:14 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/ramsayleung/rspotify/pull/211
Author: @ramsayleung
Created: 5/9/2021
Status: ✅ Merged
Merged: 9/7/2021
Merged by: @marioortizmanero

Base: master ← Head: ramsay_use_ci_to_publish_crate

📝 Commits (10+)

f887e93 Use Github Action to automatically publish crate to crate.io
f3c4160 Merge branch 'master' into ramsay_use_ci_to_publish_crate
1b9aadf Add bash script to publish crates
e5d3eb2 Add new lines
8fa008d fix path error
c40781a make publish.sh executable
84a0a8a Remove unnecessary line
46f242b remove git config
6aa9b92 remove git config
e4a9c77 Merge branch 'ramsay_use_ci_to_publish_crate' of github.com:ramsayleung/rspotify into ramsay_use_ci_to_publish_crate

📊 Changes

2 files changed (+46 additions, -0 deletions)

View changed files

➕ .github/workflows/publish.yaml (+29 -0)
➕ tools/publish.sh (+17 -0)

📄 Description

Description

Adding a continuous deployment flow with Github Action that automatically publish everything to crates.io once a tag is published

Motivation and Context

Fixed #210

Dependencies

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How Has This Been Tested?

After this PR merged, creating a new tag named 0.10 and check if the Continuous Deployment flow works. Is there a better way to test?

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/ramsayleung/rspotify/pull/211 **Author:** [@ramsayleung](https://github.com/ramsayleung) **Created:** 5/9/2021 **Status:** ✅ Merged **Merged:** 9/7/2021 **Merged by:** [@marioortizmanero](https://github.com/marioortizmanero) **Base:** `master` ← **Head:** `ramsay_use_ci_to_publish_crate` --- ### 📝 Commits (10+) - [`f887e93`](https://github.com/ramsayleung/rspotify/commit/f887e930c6cffe770185559a6e015576d834ca37) Use Github Action to automatically publish crate to crate.io - [`f3c4160`](https://github.com/ramsayleung/rspotify/commit/f3c4160edafa6fbfde0092cd643195ddee8ce49a) Merge branch 'master' into ramsay_use_ci_to_publish_crate - [`1b9aadf`](https://github.com/ramsayleung/rspotify/commit/1b9aadfcf399e0abe0f18a2ace885729dfe87233) Add bash script to publish crates - [`e5d3eb2`](https://github.com/ramsayleung/rspotify/commit/e5d3eb2c23c40b00288443cbb66a225617b39eed) Add new lines - [`8fa008d`](https://github.com/ramsayleung/rspotify/commit/8fa008df32e4af17f58bfb27f276fe214d9618e1) fix path error - [`c40781a`](https://github.com/ramsayleung/rspotify/commit/c40781a6a20064d3bb2ac5df0096983a7b8122e6) make publish.sh executable - [`84a0a8a`](https://github.com/ramsayleung/rspotify/commit/84a0a8aa6176ff368b73afcaf2585d8dfee39581) Remove unnecessary line - [`46f242b`](https://github.com/ramsayleung/rspotify/commit/46f242b228d81ff5ad1448591e6dbf084e66178e) remove git config - [`6aa9b92`](https://github.com/ramsayleung/rspotify/commit/6aa9b92a08e1d3a5ee9fea0bf27d3297eb414b20) remove git config - [`e4a9c77`](https://github.com/ramsayleung/rspotify/commit/e4a9c77f375a9a2178f6038b570e98e20ca7bbd8) Merge branch 'ramsay_use_ci_to_publish_crate' of github.com:ramsayleung/rspotify into ramsay_use_ci_to_publish_crate ### 📊 Changes **2 files changed** (+46 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/publish.yaml` (+29 -0) ➕ `tools/publish.sh` (+17 -0) </details> ### 📄 Description ## Description Adding a continuous deployment flow with Github Action that automatically publish everything to `crates.io` once a tag is published ## Motivation and Context Fixed #210 ## Dependencies ## Type of change Please delete options that are not relevant. - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update ## How Has This Been Tested? After this PR merged, creating a new tag named `0.10` and check if the Continuous Deployment flow works. Is there a better way to test? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>