Skip to content

Commit

Permalink
Devdocs: move the "making a new release" instructions to a separate M…
Browse files Browse the repository at this point in the history
…arkdown file (#67)
  • Loading branch information
DilumAluthge committed Jun 2, 2024
1 parent 5e8d9f4 commit abe0614
Show file tree
Hide file tree
Showing 2 changed files with 25 additions and 26 deletions.
26 changes: 0 additions & 26 deletions devdocs/local_setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,29 +48,3 @@ make clean
```

When you are ready, you can commit your changes and push them to your PR.

## 4. Making a new release

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
```
25 changes: 25 additions & 0 deletions devdocs/making_a_new_release.md
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
```

0 comments on commit abe0614

Please sign in to comment.