aevgarik/paperclip
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: reset lockfile changes before release publish

Browse Source
This commit is contained in:
Dotta
2026-03-17 14:53:23 -05:00
parent 824a297c73
commit f1a0460105
2 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.github/workflows/release.yml vendored
View File

@@ -92,6 +92,9 @@ jobs:
- name: Install dependencies - name: Install dependencies
run: pnpm install --no-frozen-lockfile run: pnpm install --no-frozen-lockfile
- name: Restore tracked install-time changes
run: git checkout -- pnpm-lock.yaml
- name: Configure git author - name: Configure git author
run: | run: |
git config user.name "github-actions[bot]" git config user.name "github-actions[bot]"
@@ -218,6 +221,9 @@ jobs:
- name: Install dependencies - name: Install dependencies
run: pnpm install --no-frozen-lockfile run: pnpm install --no-frozen-lockfile
- name: Restore tracked install-time changes
run: git checkout -- pnpm-lock.yaml
- name: Configure git author - name: Configure git author
run: | run: |
git config user.name "github-actions[bot]" git config user.name "github-actions[bot]"

1
doc/RELEASE-AUTOMATION-SETUP.md
View File

@@ -16,6 +16,7 @@ Note:
- the release workflows intentionally use `pnpm install --no-frozen-lockfile` - the release workflows intentionally use `pnpm install --no-frozen-lockfile`
- this matches the repo's current policy where `pnpm-lock.yaml` is refreshed by GitHub automation after manifest changes land on `master` - this matches the repo's current policy where `pnpm-lock.yaml` is refreshed by GitHub automation after manifest changes land on `master`
- the publish jobs then restore `pnpm-lock.yaml` before running `scripts/release.sh`, so the release script still sees a clean worktree
## 1. Merge the Repo Changes First ## 1. Merge the Repo Changes First