fix: actually stage the checks/publish split
The previous commit renamed release.yaml to ci.yml but never staged the content edit underneath it (git mv picked up the last-staged version, not the unstaged working-tree changes) - it pushed with the filename changed but the workflow itself untouched. This is the content that commit was supposed to carry.
This commit is contained in:
+22
-4
@@ -1,12 +1,12 @@
|
||||
name: Release
|
||||
name: CI
|
||||
|
||||
on:
|
||||
push:
|
||||
tags:
|
||||
- "v*.*.*"
|
||||
pull_request:
|
||||
|
||||
jobs:
|
||||
release:
|
||||
checks:
|
||||
name: Checks
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: https://github.com/actions/checkout@v4
|
||||
@@ -26,6 +26,24 @@ jobs:
|
||||
- run: pnpm run format:check
|
||||
- run: pnpm run test
|
||||
|
||||
publish:
|
||||
name: Publish to npm registry
|
||||
if: startsWith(github.ref, 'refs/tags/')
|
||||
needs: checks
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: https://github.com/actions/checkout@v4
|
||||
|
||||
- uses: https://github.com/pnpm/action-setup@v4
|
||||
with:
|
||||
version: 11.21.0
|
||||
|
||||
- uses: https://github.com/actions/setup-node@v4
|
||||
with:
|
||||
node-version: 22
|
||||
|
||||
- run: pnpm install --frozen-lockfile
|
||||
|
||||
- name: Set package version from the tag
|
||||
run: npm pkg set version="${GITHUB_REF_NAME#v}"
|
||||
|
||||
|
||||
Reference in New Issue
Block a user