deps: upgrade all dependencies to latest - #127
Merged
Merged
Conversation
Bump pnpm 11.9.0 to 11.11.0 (packageManager). Avoided 11.12.0 and
11.13.0, which npm marks as broken releases whose self-installer
crashes in CI ("Cannot use 'in' operator to search for 'integrity'").
11.11.0 is the newest non-broken release older than the 7-day cooldown
window. All other direct dependencies are already at their newest
installable versions; newer releases (astro 7.1.x, tailwindcss 4.3.3,
typescript-eslint 8.64.0, eslint-plugin-astro 3.0.1) fall within the
7-day release-age cooldown and were held. TypeScript held at 6.0.x
because typescript-eslint caps its typescript peer at <6.1.0.
Local validation green: install --frozen-lockfile, eslint, astro check,
tsc --noEmit, and vitest (16 tests) all pass on pnpm 11.11.0.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 432a6b03-48c5-46a1-9299-cf6938877d5b
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
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.
Summary
Aggregate dependency upgrade for
jongio/azd-web-core.11.9.0to11.11.0(packageManagerfield; CIpnpm/action-setupreads this to select the pnpm version).The lockfile is unchanged: every other direct dependency is already at its newest installable version.
Why 11.11.0 and not newer
pnpm
11.12.0and11.13.0are marked broken on npm ("This release is broken. Please upgrade to v11.13.1 or newer") and their self-installer crashes inpnpm/action-setupduring CI.11.11.0(published 2026-07-09) is the newest non-broken release that also clears the 7-day release-age cooldown.11.13.1+ and11.14.0are still inside the cooldown window.Held by the 7-day release-age cooldown
These newer releases were published within the last 7 days, so they were intentionally skipped:
TypeScript stays at
6.0.x: typescript-eslint caps itstypescriptpeer at<6.1.0, so7.0.2is not installable.Validation (local, pnpm 11.11.0)
pnpm install --frozen-lockfile: passpnpm lint(eslint): passpnpm check(astro check): pass, 0 errors, 0 warningspnpm typecheck(tsc --noEmit): passpnpm test(vitest): pass, 16 testsPlease do not merge from here: the dependency orchestrator monitors CI and merges centrally.