Skip to content

chore(deps): lock file maintenance - #355

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (in timezone UTC)

  • Branch creation
    • "before 6am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added agent:deps Renovate PR handed to the agent reviewer dependencies labels Nov 16, 2026
@renovate
renovate Bot enabled auto-merge (squash) November 16, 2026 00:57

@pptx-ts-reviewer pptx-ts-reviewer Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't judge this change, so there is no approval. Every read of the PR head in this run came back filtered by the integrity policy as below the level I'm allowed to see: the diff, the changed-file list, the head commit. I never saw a line of the 561 added. An approval from me would merge this with no human looking, and I won't approve a diff I haven't read.

What I did verify, from sources the filter allowed:

  • One commit, one changed file, +561/-550, on top of current main. Every signal says that file is pnpm-lock.yaml: lock file maintenance rewrites the lockfile only, the PR body says "All locks refreshed", and the churn fits the 5708-line lockfile rather than any manifest. That is inference, not a read of the file list.
  • Nothing reached consumers. No manifest changed, the required Protected paths check passed on the head, and every CI job ran pnpm install --frozen-lockfile green, so the refreshed lockfile satisfies the unchanged manifests.
  • The renovate.json holds hold by construction. @types/node is ^24.19.2 in the manifest, tools/api-docs pins typescript 6.0.3 exactly, and typescript-6 aliases 6.0.3. A green frozen install cannot lock a version outside those ranges.
  • CI is green on the head across the matrix, and minimumReleaseAgeStrict makes the install itself prove every locked package is at least a day old.
  • What no gate covered: which packages the refresh moved, and whether it added a package the base lockfile didn't have. That is the one check in the agent contract that needs the diff, and I couldn't do it.

I have no tool to add needs-maintainer, so this comment is the stop. Skim the diff and merge by hand, or fix the reviewer's read path so the next agent:deps review can read what it approves. Nothing here says the PR is wrong; it says I couldn't read it.

Generated by Agent PR review for #355 · claude · glm53 · ~27 AIC · ⌖ ~5 AIC · ⊞ 15.2K

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 09a4f8c to 56622d4 Compare November 17, 2026 03:17

@pptx-ts-reviewer pptx-ts-reviewer Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still no verdict, and for the same reason as my review on the old head: the integrity policy filtered every read of this PR's content. This run it blocked the file list, the diff, the head commit detail, the head tree, and a single-file fetch of pnpm-lock.yaml at refs/pull/355/head. That earlier review carried no findings, only this blocker, and it is unchanged on head 56622d4. I have not seen a line of the diff, this approval would merge the PR with no human looking, so I am not giving it.

What the allowed reads did pin down:

  • No manifest changed. One file changed, and every CI job that builds anything installs with pnpm install --frozen-lockfile green, which fails when an edited package.json no longer matches the lockfile. So the renovate.json holds hold by construction: the unchanged manifests keep @types/node at ^24.19.2, tools/api-docs on typescript 6.0.3, and the typescript-6 alias at 6.0.3.
  • No protected path changed. Protected paths compared the merge base to the head and passed, so .github/, scripts/release*, scripts/sync-version.mjs and tsdown.config.ts are untouched, and root package.json moved at most inside devDependencies, which the frozen install already rules out.
  • The one changed file is therefore pnpm-lock.yaml by elimination: a single commit from Renovate's lock-file-maintenance branch, +561/-550 against a 5708-line base lockfile. Any other reading needs Renovate to have written a file its maintenance flow does not write.
  • A new install-script package would stay inert. pnpm-workspace.yaml allowBuilds admits only @parcel/watcher and esbuild, and if the lockfile is the changed file that list did not move; pnpm skips builds for everything else. But noticing such a package in the refresh is the one check the pipeline assigns to this review rather than to CI, and I could not do it.

Everything above is also enforced by gates that run without me. The one check only a diff-reading reviewer performs is the one the filter blocked. Your options are as before: skim the diff and merge by hand, your own approval merges it, or restore the reviewer's read path so the next Monday refresh gets judged on its content. Nothing I could read says the PR is wrong.

Generated by Agent PR review for #355 · claude · glm53 · ~24 AIC · ⌖ ~6 AIC · ⊞ 16K

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agent:deps Renovate PR handed to the agent reviewer dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants