Skip to content

Commit 4f71a7f

Browse files
DavertMikclaude
andcommitted
ci: use plain SemVer release tags, no v prefix
Read github.event.release.tag_name directly as the package version. Tags like `0.4.0` or `0.5.0-beta.1` are the norm — no `v0.4.0`. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent 0f5b084 commit 4f71a7f

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

.github/workflows/publish.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,8 @@ name: Publish to npm
55
# is cryptographically linked to this repo (codeceptjs/reflection) and the
66
# exact workflow run that built it.
77
#
8-
# Tag the release with a SemVer tag like `v0.4.0` or `v0.5.0-beta.1`.
8+
# Tag the release with a plain SemVer tag like `0.4.0` or `0.5.0-beta.1`
9+
# (no `v` prefix).
910
# - Stable tags (no prerelease suffix) publish under the default `latest` dist-tag.
1011
# - Prereleases (alpha/beta/rc) publish under the `beta` dist-tag.
1112

@@ -53,8 +54,7 @@ jobs:
5354

5455
- name: Set package version from release tag
5556
run: |
56-
TAG="${{ github.event.release.tag_name }}"
57-
VERSION="${TAG#v}"
57+
VERSION="${{ github.event.release.tag_name }}"
5858
echo "Publishing @codeceptjs/reflection version $VERSION"
5959
npm version "$VERSION" --no-git-tag-version
6060

0 commit comments

Comments
 (0)