chore: version packages#44
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
simplepdf-webhooks | 0b02181 | Commit Preview URL Branch Preview URL |
Jun 30 2026, 08:22 AM |
bendersej
added a commit
that referenced
this pull request
Jun 30, 2026
…ollout) (#45) ## Background `@simplepdf/react-embed-pdf` depended on `@simplepdf/embed` via a caret range (`^0.6.0`), so a consumer installing react resolves embed to whatever `0.6.x` npm offers at install time, not necessarily the build react was tested against. ## Changes - Pin react's `@simplepdf/embed` dependency to the exact `0.6.0` (was `^0.6.0`), so a published `@simplepdf/react-embed-pdf` always installs the exact embed build it ships with. - Sync the lockfile. - Add a `@simplepdf/react-embed-pdf` `patch` changeset. ## Notes - **Full rollout control:** moving react's embed version becomes a deliberate release step (changesets updates the exact pin and bumps react together), not a caret resolved at the consumer's install time. - This pin depends on `@simplepdf/embed@0.6.0` actually being published (the `#44` version bump). npm currently still shows `0.5.0`, so confirm the `0.6.0` publish has landed before/with this release.
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@simplepdf/embed@0.6.0
Minor Changes
e91b4c7: Add a TanStack AI adapter (the
/tanstack-aisubpath) for client-side tool calling, alongside the existing Vercel AI SDK (/ai-sdk) adapter. Both wrap the same generated tool registry + bridge router, so the editor is drivable from either SDK with no duplicated logic.@simplepdf/embed/tanstack-ai:simplePDFToolDefinitions()(server, forchat({ tools })) andcreateSimplePDFTools({ embed })(browser.client()tools forclientTools(...)thenuseChat({ tools })).@simplepdf/react-embed-pdf/tanstack-ai:useEmbedTools(embedRef), the editor-bound client tools. Server definitions stay in the React-free core@simplepdf/embed/tanstack-ai, so a server route never pulls React in.@tanstack/aiis a new optional peer, pulled only by the/tanstack-aisubpath; the package roots stay free of it (and ofzod).@simplepdf/embedroot drops the internal helpersbuildEditorDomain,encodeContext,isBridgeResultLike.@simplepdf/embed/protocoldrops the internalINTERNAL_PROTOCOL/InternalProtocolType(used only by the bridge).@simplepdf/react-embed-pdfroot no longer re-exports the whole@simplepdf/embedcore or the wire-protocol vocabulary; import those from@simplepdf/embed/@simplepdf/embed/protocoldirectly.@simplepdf/react-embed-pdf/ai-sdkno longer re-exportssimplePDFToolDefinitions(import it from@simplepdf/embed/ai-sdk); the browser-sidecreateSimplePDFExecutorstays. Server tool-definitions now live only in the React-free core, so a server route never pulls React in.@simplepdf/react-embed-pdf@1.12.0
Minor Changes
e91b4c7: Add a TanStack AI adapter (the
/tanstack-aisubpath) for client-side tool calling, alongside the existing Vercel AI SDK (/ai-sdk) adapter. Both wrap the same generated tool registry + bridge router, so the editor is drivable from either SDK with no duplicated logic.@simplepdf/embed/tanstack-ai:simplePDFToolDefinitions()(server, forchat({ tools })) andcreateSimplePDFTools({ embed })(browser.client()tools forclientTools(...)thenuseChat({ tools })).@simplepdf/react-embed-pdf/tanstack-ai:useEmbedTools(embedRef), the editor-bound client tools. Server definitions stay in the React-free core@simplepdf/embed/tanstack-ai, so a server route never pulls React in.@tanstack/aiis a new optional peer, pulled only by the/tanstack-aisubpath; the package roots stay free of it (and ofzod).@simplepdf/embedroot drops the internal helpersbuildEditorDomain,encodeContext,isBridgeResultLike.@simplepdf/embed/protocoldrops the internalINTERNAL_PROTOCOL/InternalProtocolType(used only by the bridge).@simplepdf/react-embed-pdfroot no longer re-exports the whole@simplepdf/embedcore or the wire-protocol vocabulary; import those from@simplepdf/embed/@simplepdf/embed/protocoldirectly.@simplepdf/react-embed-pdf/ai-sdkno longer re-exportssimplePDFToolDefinitions(import it from@simplepdf/embed/ai-sdk); the browser-sidecreateSimplePDFExecutorstays. Server tool-definitions now live only in the React-free core, so a server route never pulls React in.Patch Changes