Version Packages#990
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
July 16, 2026 17:41
ac5cbf9 to
c16c443
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 16, 2026 19:08
c16c443 to
fe5bee9
Compare
EvanReinstein
approved these changes
Jul 16, 2026
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.
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
@paypal/paypal-js@10.1.0
Minor Changes
PayPalMessagesSession.fetchContentto returnPromise<MessageContent>(previouslyPromise<MessageContent | null>). The evergreen SDK never resolves tonull— on an API error it returns an empty sentinelMessageContent(emptymessageItems) so the<paypal-message>element recognizes the error state and collapses. Existing=== nullchecks against the result become dead code but continue to compile.Patch Changes
processOptions. Theenvironmentoption was still read via destructuring, which reads through the prototype chain, soObject.prototype.environment = "sandbox"could downgrade a production checkout to the sandbox SDK URL.environmentis now read with ahasOwnPropertyguard, matching the existingsdkBaseUrlprotection.@paypal/react-paypal-js@10.2.0
Minor Changes
useBraintreePayPalMessages, a v6 hook for rendering PayPal promotional / BNPL messaging (<paypal-message>) via Braintree.BraintreePayPalCheckoutInstance.createMessageson the shared instance fromuseBraintreePayPal. Because Braintree'screateMessagesis asynchronous (unlike the PayPal SDK's synchronouscreatePayPalMessages), the instance is created in an effect that awaits the Promise and guards against unmount / instance change before storing it.error,isReady,isLoading, andhandleFetchContent(options), which fetches message content for a<paypal-message>element and resolves to a content object exposingupdate({ amount })so the displayed amount can change without re-fetching.Braintree PayPal context error: …), distinct from instance/fetch errors, so consumers can tell which layer failed.BraintreeMessagesOptions,BraintreeMessagesInstance,BraintreeMessageContent, andBraintreeFetchMessageContentOptionstypes, pluscreateMessagesonBraintreePayPalCheckoutInstance.Patch Changes
dist/tsconfig.lib.tsbuildinfo) in the published npm package. The build-info file is now written tonode_modules/.cache/tsc/instead ofdist/, trimming ~72 kB unpacked (~25 kB gzipped) from the tarball. No functional or API change — the library output is byte-identical.