@circle-fin/provider-cctp-v2 1.0.3 → 1.0.5

package/CHANGELOG.md

@@ -1,5 +1,55 @@
 # @circle-fin/provider-cctp-v2
 
+## 1.0.5
+
+### Patch Changes
+
+- Improved how the retry function handles bridge transfers stuck in a pending state:
+  - The retry function now properly waits for pending transactions to complete before continuing with the next steps, instead of failing or skipping them
+  - Validates that required data (like transaction hashes) is present before attempting to continue, throwing clear errors immediately instead of failing silently
+  - Error messages now clearly indicate when "user action is required" for non-actionable states
+  - Validation errors during pending state resolution are no longer silently caught and now surface properly
+
+- Fix retry functionality when a custom `recipientAddress` is specified in bridge parameters. Previously, retry operations would fail attestation validation because the `recipientAddress` was not preserved in the bridge result, causing the system to use the adapter address instead of the originally specified recipient.
+- Validation errors now use standardized error codes for consistent error handling. All validation failures return the same `KitError` structure as other SDK errors.
+
+  **Migration:** If you're catching validation errors, update your error handling:
+  - Check `error.code === 1098` instead of `instanceof ValidationError`
+  - Access details via `error.cause?.trace?.validationErrors` instead of `error.errors`
+
+  The legacy `ValidationError` class remains available for backward compatibility.
+
+- **Improved retry() behavior for completed bridges**
+
+  -The `retry()` method now handles completed bridge operations gracefully:
+  Calling `retry()` on an already-completed bridge now returns successfully instead of throwing an error
+
+## 1.0.4
+
+### Patch Changes
+
+- Fixed bug where tokens could be burned when bridging to unsupported chains, and improved error messages to clearly show which chains are supported.
+
+  **What's Fixed:**
+  - **Prevents fund loss**: Bridge operations now fail immediately if your adapter doesn't support the source or destination chain, **before** any tokens are approved or burned. Previously, tokens could be burned on the source chain before discovering the destination chain was unsupported, requiring manual recovery.
+  - **Better error messages**: When you attempt to use an unsupported chain, the error now clearly lists all chains your adapter supports, making it easy to pick an alternative:
+    ```
+    Invalid chain 'Linea Sepolia': Not supported by this adapter.
+    It supports 17 chains: Arbitrum, Base, Ethereum, Polygon, Solana, ...
+    ```
+  - **Correct error codes**: Chain validation errors now use the correct `INVALID_CHAIN` error code instead of `UNSUPPORTED_ROUTE`, making it easier to handle errors programmatically.
+
+- Improved error handling with more informative and consistent error messages.
+
+  Errors now include:
+  - Specific error codes for programmatic handling
+  - Error type categorization (BALANCE, ONCHAIN, RPC, NETWORK)
+  - Recoverability information (FATAL vs RETRYABLE)
+  - Clearer error messages with chain context
+  - Original error details preserved for debugging
+
+- Fixed an issue where bridging USDC to Solana would fail when specifying a recipient address different from the transaction signing wallet. The adapter now correctly creates the Associated Token Account (ATA) for the specified recipient address and delivers USDC to that address.
+
 ## 1.0.3
 
 ### Patch Changes