chore: npm-check-updates && pnpm update - #326
Merged
Merged
Conversation
team-cdktn
added
auto-approve
ci/run-all
open-constructs-cdktn
Bot
force-pushed
the
automation/pnpm-upgrade
branch
from
July 20, 2026 07:22
068c23a to
983fe57
Compare
open-constructs-cdktn
Bot
force-pushed
the
automation/pnpm-upgrade
branch
2 times, most recently
from
August 3, 2026 07:41
2822497 to
5eb7846
Compare
open-constructs-cdktn
Bot
force-pushed
the
automation/pnpm-upgrade
branch
2 times, most recently
from
August 17, 2026 04:54
21b25ed to
33e4c13
Compare
open-constructs-cdktn
Bot
force-pushed
the
automation/pnpm-upgrade
branch
from
August 24, 2026 04:57
33e4c13 to
438abb1
Compare
Ran npm-check-updates and pnpm update to keep the `pnpm-lock.yaml` file up-to-date.
open-constructs-cdktn
Bot
force-pushed
the
automation/pnpm-upgrade
branch
from
September 9, 2026 13:05
438abb1 to
eef4ec1
Compare
The upgrade pulls in @parcel/watcher transitively, and pnpm recorded the pending build-script decision in allowBuilds as a placeholder. Set it to false: the package ships prebuilt binaries as per-platform optional dependencies, and its install script is only the build-from-source fallback, so there is nothing we need it to run. Verified with a strict `pnpm ci` on this branch: exits 0 with no ERR_PNPM_IGNORED_BUILDS and no ignored-builds warning. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Prettier 3.9.6 collapses leading-pipe unions onto one line where they fit. This is the mechanical `prettier --write` result; no behaviour changes. Clears both Quality / prettier and the prettier/prettier lint failures, which flagged the same 11 files. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
main moved to TypeScript 6 for the remaining packages (#406), which collided with this branch's ncu bumps in pnpm-lock.yaml. The manifests merged cleanly; only the lockfile conflicted, so it was regenerated from the merged package.json set rather than hand-resolved. Verified: `pnpm ci` exits 0 against the regenerated lockfile, and `prettier --check` is clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
knip 6.35.1 was published ~6h before the upgrade ran, inside pnpm's 24h minimumReleaseAge window. pnpm did not block it; it recorded the exception in minimumReleaseAgeExclude and carried on, which waives the delay that the policy exists to enforce. Roll knip back to main's ^6.16.1 / 6.16.1 and remove the exclude entry, so the lockfile satisfies the policy on its own. Reverting the range alone was not enough: 6.35.1 still satisfies ^6.16.1, so the resolution had to be pinned back as well. Verified: `pnpm ci` passes the supply-chain policy check over all 1532 lockfile entries with no exclusions, and prettier is clean. knip 6.16.1 is the version main already runs, and Quality / knip passed with it on #406. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
jsteinich
approved these changes
Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ran npm-check-updates and pnpm update to keep the
pnpm-lock.yamlfile up-to-date.