From 523818ea9bf81f96abf4e6b73e81c2ce87518c07 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Fri, 6 Nov 2026 12:19:36 +0000 Subject: [PATCH] chore(lockfile): refresh pnpm-lock.yaml (#19443) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Thinking Path > - Paperclip uses a dependency lock for reproducible builds. > - Dependency changes on master need matching lock entries. > - Paid eval reports also pin a reviewed offline correction. > - Reports must install before paid model work starts. > - This automated PR keeps the lock and report proof together. ## Linked Issues or Issue Description **What happened?** Dependency manifests on master changed after the last committed lock refresh. **Expected behavior** Frozen installs must match those manifests. Eval reports must retain matching offline lock proof. **Steps to reproduce** Run a frozen install before and after this lock refresh. ## What Changed - Refresh the dependency lock from the manifests on master. - Include the matching offline report correction and hashes. ## Verification - Pinned pnpm resolution completed with lifecycle scripts disabled. - The report proof refresh accepted the reviewed committed baseline. - The workflow rejected changes outside the lock and report proof files. ## Risks The lockfile bot merges this PR without CI or review when every added package version is at least 3 days old on npm. Otherwise the PR waits for a maintainer, and the daily refresh tries again. The bot merges only the exact commit this workflow generated from manifests already reviewed on master. Unknown report lock baselines remain blocked. This update changes no permissions or paid enable gates. ## Model Used None — generated by pnpm and the deterministic report-lock updater. ## Checklist - [x] Thinking path and problem description included - [x] Generated lock and matching report proof included - [x] Release-age gate decides between bot merge and maintainer review Co-authored-by: lockfile-bot --- pnpm-lock.yaml | 3 +++ tests/runner-e2e/report-lock.json | 6 +++--- tests/runner-e2e/report-lock.patch | 14 ++++++++++++++ 3 files changed, 20 insertions(+), 3 deletions(-) diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index 45b3aaf615e..a87f8e749f5 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -1306,6 +1306,9 @@ importers: lucide-react: specifier: ^1.48.0 version: 1.48.0(react@19.2.8) + mdast-util-from-markdown: + specifier: ^2.0.3 + version: 2.0.3 mermaid: specifier: ^12.1.0 version: 12.1.0 diff --git a/tests/runner-e2e/report-lock.json b/tests/runner-e2e/report-lock.json index 26811314f90..bd6c65c89b8 100644 --- a/tests/runner-e2e/report-lock.json +++ b/tests/runner-e2e/report-lock.json @@ -1,6 +1,6 @@ { "inputSha256": "14049cb20d48f448b6f24e5445a75bf8d22ed3052fe9ff885f4c127775d958d3", - "outputSha256": "14049cb20d48f448b6f24e5445a75bf8d22ed3052fe9ff885f4c127775d958d3", - "patchSha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855", - "basis": "Admitted by the trusted master lockfile refresh after a verified Dependabot lockfile merged. No correction is needed." + "outputSha256": "53f6c7c7f09a5cf0442ee2992a656eb2336ab6b13e665219a0cd1247475f13d9", + "patchSha256": "eb4adb2f3c8a2ebefe65d3100b581c5765318023d96aa8a80394c848d7299b9d", + "basis": "Generated with the trusted master lockfile refresh. Review this offline correction and its hashes with the dependency changes." } diff --git a/tests/runner-e2e/report-lock.patch b/tests/runner-e2e/report-lock.patch index e69de29bb2d..6e5bb651368 100644 --- a/tests/runner-e2e/report-lock.patch +++ b/tests/runner-e2e/report-lock.patch @@ -0,0 +1,14 @@ +diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml +index 45b3aaf..a87f8e7 100644 +--- a/pnpm-lock.yaml ++++ b/pnpm-lock.yaml +@@ -1306,6 +1306,9 @@ importers: + lucide-react: + specifier: ^1.48.0 + version: 1.48.0(react@19.2.8) ++ mdast-util-from-markdown: ++ specifier: ^2.0.3 ++ version: 2.0.3 + mermaid: + specifier: ^12.1.0 + version: 12.1.0