Skip to content

Commit 2f7597f

Browse files
committed
chore: update release process
1 parent 810feaf commit 2f7597f

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

.github/workflows/release.yml

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,18 +12,20 @@ jobs:
1212
with:
1313
fetch-depth: '0'
1414

15-
- uses: paulhatch/semantic-version@v5.3.0
15+
- name: Get Next Version
1616
id: semantic_version
17+
uses: ietf-tools/semver-action@v1
1718
with:
18-
tag_prefix: "v"
19+
token: ${{ github.token }}
20+
branch: main
1921

2022
- name: Create tag
21-
run: git tag ${{ steps.semantic_version.outputs.version }}
23+
run: git tag ${{ steps.semver.outputs.next }}
2224

2325
- name: Push tag
2426
run: git push --tags
2527

2628
- name: Release
27-
run: gh release create ${{ steps.semantic_version.outputs.version }} --generate-notes
29+
run: gh release create ${{ steps.semver.outputs.next }} --generate-notes
2830
env:
2931
GH_TOKEN: ${{ github.token }}

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,5 +130,5 @@ The title of the PR is what is used to generate the labels.
130130

131131
## Merging PRs
132132

133-
We use a [GitHub Action](https://github.com/PaulHatch/semantic-version) to compute the version based on conventional commit messages, push a tag with the computed version, then use
133+
We use a [GitHub Action](https://github.com/marketplace/actions/semver-conventional-commits) to compute the version based on conventional commit messages, push a tag with the computed version, then use
134134
the [GitHub Release CLI](https://cli.github.com/manual/gh_release_create) to generate release notes based on labels.

0 commit comments

Comments
 (0)