deps: upgrade all dependencies to latest#298
Merged
Merged
Conversation
npm/pnpm: no actionable upgrades this cycle. Every direct dependency across the workspace (root + sdk, cli, mcp, web, vscode) is already at its latest stable. pnpm 11.15.0 was published within the 7-day release cooldown, so packageManager stays at 11.14.0. GitHub Actions: upgrade the GitHub Pages deploy actions to their newest generation (checkout/setup-node/upload-artifact/pnpm were already at latest SHA pins): - actions/configure-pages v5 -> v6.0.0 - actions/upload-pages-artifact v3 -> v5.0.0 - actions/deploy-pages v4.0.5 -> v5.0.0 The only breaking change in this set (upload-pages-artifact v4+ excludes dotfiles from the uploaded artifact) does not affect this deploy: the web public/ folder has no dotfiles and vite emits assets/ paths, so no _* or .* files are dropped. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 38a45b86-1cd2-4bcd-bbaf-54bfa386fb05
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
1 participant
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
Autonomous dependency-upgrade pass across every ecosystem in the repo.
npm / pnpm: no actionable upgrades this cycle
Every direct dependency across the workspace (root plus
sdk,cli,mcp,web,vscode) is already at its latest stable release. This repo runs a daily deps upgrade and #292 merged yesterday, so the tree was already current.ncu --deep --registry https://registry.npmjs.org/reports all 5 packages match latest.pnpm 11.15.0was published inside the 7-day release cooldown, sopackageManagerintentionally stays at11.14.0.overrides(form-data, hono, esbuild) already cover latest via their caret ranges.GitHub Actions: Pages deploy actions bumped to newest generation
checkout,setup-node,upload-artifact, andpnpm/action-setupwere already pinned to their latest SHAs. The Pages deploy actions were a few generations behind, so this PR moves them forward (SHA-pinned, verified against each release tag):actions/configure-pagesv5 -> v6.0.0actions/upload-pages-artifactv3 -> v5.0.0actions/deploy-pagesv4.0.5 -> v5.0.0Breaking-change review
The only breaking change in this set is that
upload-pages-artifactv4+ excludes dotfiles from the uploaded artifact. Verified non-impacting for this deploy: the webpublic/folder has no dotfiles (no.nojekyll), and vite'sbase: "./"emitsassets/paths, so no_*or.*files are dropped from the published site.Validation
pnpm -r buildgreen (all 5 packages)pnpm -r typecheckgreenpnpm lint(biome) clean, 425 filespnpm -r testgreen: sdk 548, mcp 78, vscode 407, web 952 (web re-run with--no-file-parallelismto clear machine-load worker-startup flakiness)Only
.github/workflows/pages.ymlchanged; nopackage.jsonor lockfile changes.