deps: bump @json-render/{core,react,vue} to v0.20.0 - #288
Merged
Conversation
No source changes required: this repo's action bridges (packages/json-render-ui/src/action-bridge.ts and the hub-next React port) plug into JSONUIProvider's stable handlers prop, not the core ActionExecutionContext.executeAction callback affected by v0.20.0's breaking change.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
bump.config.ts imports tinyexec directly (added in the v0.9.5 release script), but it was never listed in the root package.json - only pulled in transitively via bumpp. knip's unlisted-dependencies check has been failing main's CI Lint job since that change; add the explicit catalog:deps entry to fix it.
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.
Summary
Bumps the
@json-render/core,@json-render/react, and@json-render/vuepnpm catalog entries from^0.19.0to^0.20.0.Why no source changes
v0.20.0's only breaking change affects custom renderer bridges that implement the core
ActionExecutionContext.executeActioncallback (it now receives a fullActionBindinginstead of a bare action name). This repo's action bridges —packages/json-render-ui/src/action-bridge.tsand the React port inexamples/hub-next/src/client/json-render/react-renderer.tsx— plug intoJSONUIProvider'shandlers: Record<string, ActionHandler>prop, a stable surface unchanged between v0.19.0 and v0.20.0. Neither implements the lower-levelexecuteActioncallback, so no code changes were required.The other v0.20.0 additions (named slots, nested
$item-relative repeats, dangling-child pruning,visiblefield optionality) touch spec-structural fields devframe's schema/validation layer deliberately passes through unchecked, so they don't require migration either — they're available for specs to use going forward.Verification
pnpm install— lockfile updated,@json-render/{core,react,vue}resolve to0.20.0pnpm build— 27/27 tasks succeededpnpm typecheck— 38/38 tasks succeededpnpm test— 1269 passed, 9 skipped (onehub-nexttest timed out under machine load in the full run but passes cleanly in isolation — unrelated to this change)pnpm lint— cleanpnpm knip— pre-existing unrelated failure (tinyexecunlisted dependency inbump.config.ts) reproduces identically onmain, unaffected by this changeThis PR was created with the help of an agent.