Skip to content

Commit eedbeec

Browse files
authored
Merge pull request #38 from rust-lang/document-how-to-publish-a-new-version
document how to publish a new version
2 parents dd81cd2 + b6f4e1e commit eedbeec

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

CONTRIBUTING.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,23 @@ Here are some useful links to the GitHub documentation:
102102
- [Creating a JavaScript action](https://docs.github.com/en/actions/sharing-automations/creating-actions/creating-a-javascript-action)
103103
- [OpenID Connect](https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/about-security-hardening-with-openid-connect)
104104

105+
## Publish the action
106+
107+
Once the `main` branch contains the latest changes,
108+
you can publish a new version of the action by:
109+
110+
- Creating a new tag and release by clicking on "Draft a new release" from the
111+
[GitHub releases UI](https://github.com/rust-lang/crates-io-auth-action/releases).
112+
- Pushing the changes of the `main` branch to the `v1` branch. To do so, you can run:
113+
114+
```sh
115+
git checkout main
116+
git pull
117+
git checkout v1
118+
git reset --hard main
119+
git push
120+
```
121+
105122
## FAQ
106123

107124
### Why TypeScript?

0 commit comments

Comments
 (0)