chore: version packages - #11
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
2 times, most recently
from
July 9, 2026 04:03
40f393a to
b7796d4
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
July 15, 2026 04:52
b7796d4 to
60b538a
Compare
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 master, this PR will be updated.
Releases
bridgerton@0.7.0
Minor Changes
#10
1bbd04cThanks @gorried! - Add a destination Bridge wallet option to transfer creation.#13
b54ca61Thanks @Slokh! - Addprofilecommands for end-to-end transfer latency profiling:profile runcreates transfers over a configurable route (e.g.bridge_wallet → tempo,tempo → polygon), funds crypto-source deposits from the local wallet, receives Bridge webhooks through an in-process ngrok tunnel (with an API-poll fallback for missed events), measures request→payment_processed lifecycle latency, and returns funds — for EVM destinations via measured reverse transfers so both directions get latency data.profile return-fundssweeps funds back standalone;profile summarizere-prints the latency summary for a previous run.#14
a6d219aThanks @Slokh! - Add Solana USDC and USDT as source currencies for transfer profiling.#14
a6d219aThanks @Slokh! - Support direct USDC fund returns for Bridge-wallet to EVM profiling routes when the destination is the local wallet.#12
8de150bThanks @gorried! - Add static transfer template management commands and transfer creation options for reusable Bridge payment routes.Patch Changes
#14
a6d219aThanks @Slokh! - Fix the native Optimism USDC contract address used by profile reverse transfers.#14
a6d219aThanks @Slokh! - Profile runs now wait for the Bridge wallet balance to recover after per-batch fund returns before starting the next batch, avoiding "amount exceeds available balance" failures.#14
a6d219aThanks @Slokh! - profile run now prefers webhook delivery for completion latency; API polling acts only as a fallback after a configurable --webhook-grace-seconds window