Skip to content

fix(ci): keep lockfile maintenance from bumping manifest ranges #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
altaywtf merged 1 commit into from
Aug 20, 2026
+13 −1
Merged

fix(ci): keep lockfile maintenance from bumping manifest ranges #73

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion .github/workflows/lockfile-maintenance.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,8 +62,20 @@ jobs:
with:
node-version-file: .node-version

# --no-save keeps package.json and the lockfile's specifier records at
# their committed values; without it pnpm 11 update rewrites both and a
# lockfile-only commit fails frozen installs with a specifier mismatch.
- name: Refresh transitive lockfile resolutions
run: corepack pnpm update --lockfile-only -r
run: corepack pnpm update --no-save --lockfile-only -r

- name: Assert only the lockfile changed
run: |
set -euo pipefail
if ! git diff --quiet -- ':(exclude)pnpm-lock.yaml'; then
echo "unexpected working-tree changes beyond pnpm-lock.yaml:" >&2
git status --porcelain >&2
exit 1
fi
Comment thread
altaywtf marked this conversation as resolved.

- name: Open or update pull request
env:
Expand Down