chore(deps): update dependencies - #129
Merged
Merged
Conversation
Take every compatible third-party update across all workspace members, plus the global-jsdom 29 -> 30 major (jsdom 30), which needed no code changes. @modelcontextprotocol/sdk is left for #127 and @udibo/* packages are bumped separately. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Resolves the lock against #127 and the 0.11.4 release, and moves the example and the tailwindcss template to @udibo/esbuild-plugin-postcss 0.4.2. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
🎉 This PR is included in version 0.11.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
Updates Juniper's third-party dependencies across every workspace member
(
src,example,templates/*,tutorials/blog), keeping the members on thesame ranges. Every resolved version was published before the 3-day
minimumDependencyAgecutoff (the newest is playwright 1.63.0, published2026-09-04). The policy is unchanged.
Bumps (declared range floor, resolved version)
Named in
deno outdatedjsr:@std/collections1.2.0 → 1.3.0jsr:@std/encoding1.0.10 → 1.0.11jsr:@std/streams1.1.1 → 1.1.2jsr:@std/testing1.0.19 → 1.0.20npm:esbuild0.28.0 → 0.28.2npm:global-jsdom29.0.0 → 30.0.0 (major; peerjsdom29.1.1 → 30.0.1)npm:hono4.12.23 → 4.13.7npm:isbot5.1.42 → 5.2.2 (range floor^5.1.40→^5.2.2)npm:playwright1.60.0 → 1.63.0npm:@testing-library/react16.3.2 → 16.3.3npm:@testing-library/user-event14.6.1 → 14.6.7npm:@tailwindcss/postcss4.3.0 → 4.3.3npm:tailwindcss4.3.0 → 4.3.3npm:@tanstack/react-query5.100.14 → 5.102.8npm:react-error-boundary6.1.2 → 6.1.5npm:react-router8.3.0 → 8.3.1npm:pg8.21.0 → 8.23.0npm:@types/pg8.20.0 → 8.23.1Declared-range floors raised to the locked or newer compatible version
deno updatealso moved these within their existing caret ranges:npm:react/npm:react-dom19.2.7 → 19.2.8npm:@types/react19.2.16 → 19.2.18npm:zod4.4.3 → 4.5.4jsr:@std/async^1.4.0→^1.5.0(lock already resolved 1.5.0)jsr:@std/cli^1.0.30→^1.0.32(lock already resolved 1.0.32)jsr:@std/path^1.1.5→^1.1.6Transitive lock movement includes
postcss8.5.15 → 8.5.28 and@std/data-structures1.1.1 → 1.1.2. playwright 1.63 no longer pullsfsevents.Skipped
@modelcontextprotocol/sdk1.29.0 → 1.30.0: chore(deps): drop the unused MCP SDK declaration #127 removesthat declaration, so this PR leaves it alone. Its lock entry still changes: its
zodpeer now resolves to 4.5.4, because zod is shared across the workspace.Whichever of this PR and chore(deps): drop the unused MCP SDK declaration #127 merges second needs a
deno.lockrefresh.@udibo/*(@udibo/juniper,@udibo/esbuild-plugin-postcss): bumpedseparately after their own releases.
Notes
global-jsdom 30: kept. It requires
jsdom >=30 <31. Check and every suitepass without code changes.
playwright: declared in
example/deno.jsonbut never imported, so the bumpneeds no browser binaries.
allowScripts: unchanged. It was already out of step with the lock beforethis PR:
npm:esbuild@0.27.2, but the lock resolved 0.28.0 andnow 0.28.2.
@parcel/watcher@2.5.6andless@4.5.1name packagesnot in the lock.
allowScriptsagainst the lock.rm -rf node_modules && deno installprints no lifecycle-scriptwarnings; esbuild works through its optional platform packages.
I left it alone because re-pointing the allow entry at 0.28.2 would start
running esbuild's postinstall, which does not run today.
Testing
All run locally on the final committed content (Deno 2.9.6, Linux):
deno task check: pass (check, lint, fmt,test:doc-lint,doc-lint: 9entrypoints clean)
deno task test --parallel: 33 passed (382 steps)deno task test --coverage(serial, as CI on Ubuntu): passdeno task build:prod:minimalanddeno task build:prod:tailwindcss: passdeno task test:example --parallel: 33 passed (329 steps)deno task test:minimal --parallel: 3 passed (4 steps)deno task test:tailwindcss --parallel: 3 passed (4 steps)deno task test:tanstack --parallel: 9 passed (78 steps)deno task test:blog --parallel: 3 passed (3 steps)deno task test:postgres --parallel: 4 passed (11 steps). This ran against athrowaway
postgres:18container migrated withdb:migrate:test, as in CI.deno outdated -r '!@udibo/*'afterwards lists only@modelcontextprotocol/sdk.🤖 Generated with Claude Code