Skip to content

document how to publish a new version #38

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.

Sign up for GitHub

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

Merged
marcoieni merged 1 commit into from
Jul 24, 2025
Merged

document how to publish a new version #38

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,23 @@ Here are some useful links to the GitHub documentation:
- [Creating a JavaScript action](https://docs.github.com/en/actions/sharing-automations/creating-actions/creating-a-javascript-action)
- [OpenID Connect](https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/about-security-hardening-with-openid-connect)

## Publish the action

Once the `main` branch contains the latest changes,
you can publish a new version of the action by:

- Creating a new tag and release by clicking on "Draft a new release" from the
[GitHub releases UI](https://github.com/rust-lang/crates-io-auth-action/releases).
- Pushing the changes of the `main` branch to the `v1` branch. To do so, you can run:

```sh
git checkout main
git pull
git checkout v1
git reset --hard main
git push
```

## FAQ

### Why TypeScript?
Expand Down