-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Devdocs: move the "making a new release" instructions to a separate M…
…arkdown file (#67)
- Loading branch information
1 parent
5e8d9f4
commit abe0614
Showing
2 changed files
with
25 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Making a new release of this action | ||
|
||
First, go to the [Releases](https://github.com/julia-actions/install-juliaup/releases) section of this repo and create a new release using the GitHub web interface. | ||
|
||
Once you've created the new release, you need to update the `v2` tag to point to the new release. For example, suppose that the previous release was `v2.1.0`, and suppose that you just created the new release `v2.2.0`. You need to update the `v2` tag so that it points to `v2.2.0`. Here are the steps: | ||
|
||
```bash | ||
git clone git@github.com:julia-actions/install-juliaup.git | ||
cd install-juliaup | ||
git fetch --all --prune | ||
git fetch --all --tags | ||
|
||
# Delete the current v2 tag locally: | ||
git tag -d v2 | ||
|
||
# Create a new v2 tag locally, where the new v2 tag will point to the | ||
# release that you created in the previous step. | ||
# | ||
# Make sure to change `v2.2.0` to the actual value for the release | ||
# that you just created in the previous step. | ||
git tag v2 v2.2.0 | ||
|
||
# Force-push the new v2 tag: | ||
git push --force origin v2 | ||
``` |