Skip to content

Commit

Permalink
test release gh action
Browse files Browse the repository at this point in the history
  • Loading branch information
marcopiraccini committed Dec 13, 2023
1 parent 262abc7 commit af89f27
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 17 deletions.
3 changes: 3 additions & 0 deletions .github/workflows/release-draft.yml
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ jobs:
- uses: actions/[email protected]
with:
ref: ${{ inputs.tag_name }}
fetch-depth: 0 # https://github.com/actions/checkout/issues/1471
- uses: actions/setup-node@v4
with:
node-version: 18
Expand Down Expand Up @@ -87,6 +88,7 @@ jobs:
- uses: actions/[email protected]
with:
ref: ${{ inputs.tag_name }}
fetch-depth: 0 # https://github.com/actions/checkout/issues/1471
- run: npm ci
- run: npm run build:win
- run: npm run release:win
Expand All @@ -105,6 +107,7 @@ jobs:
- uses: actions/[email protected]
with:
ref: ${{ inputs.tag_name }}
fetch-depth: 0 # https://github.com/actions/checkout/issues/1471
- uses: actions/setup-node@v4
with:
node-version: 18
Expand Down
17 changes: 0 additions & 17 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,20 +49,3 @@ $ npm run build:mac
$ npm run build:linux
```

### Prepare a release tag

Releases are created from tags, so you need to create a tag before you can create a release, e.g. if the current development version is `0.1.0`:

```bash
git pull # Make sure you have the latest changes
git tag -a v0.1.0 -m "Release 0.1.0"
git push origin v0.1.0
```

Then you have to do a version bump:
```bash
npm version --no-git-tag-version minor # or major, patch, etc.
git add package.json
git commit -m "version bump"
git push
```

0 comments on commit af89f27

Please sign in to comment.