chore: restore FE release ancestry (zero diff) - #4142
Merged
Merged
Conversation
* Publish - @synapsecns/synapse-interface@0.44.4 * fix(sdk-router): enable ETH as SBA bridge destination (#4063) Add SupportedChainId.ETH to SBA_BRIDGE_ENABLED_DESTINATION_CHAINS. The SBA adapter is deployed on ETH and tokens like HIGH are configured, but ETH was missing from the enabled destinations set so all SBA routes to Ethereum returned empty. Co-authored-by: Trajan0x <trajan0x@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Publish - @synapsecns/rest-api@1.13.39 - @synapsecns/sdk-router@0.23.3 - @synapsecns/synapse-interface@0.44.5 - @synapsecns/widget-example@0.2.5 - @synapsecns/widget@0.11.5 * Unpause DFK (#4067) * Unpause DFK * fix: use direct DFK RPCs for bridge quote providers (#4068) * fix(terraform-provider-grafanaamg): sweep expired provider tokens before minting (#4073) * fix(terraform-provider-grafanaamg): harden release publishing (#4074) * ci(terraform-provider-grafanaamg): add signing key refresh * fix(terraform-provider-grafanaamg): export protected signing key * fix(terraform-provider-grafanaamg): harden release publishing * fix(terraform-provider-grafanaamg): validate release inputs * fix(terraform-provider-grafanaamg): preserve published releases --------- Co-authored-by: Trajan0x <trajan0x@users.noreply.github.com> * Publish - @synapsecns/synapse-interface@0.45.0 * fix: restore Aurora and Cronos outbound quotes and RPC fallback (#4132) * fix(sdk-router): restore Aurora and Cronos outbound routes * fix(synapse-interface): fall back after RPC HTTP failures * test(sdk-router): defer RPC calls in skipped swap suite * style: resolve bridge quote lint violations * fix(synapse-interface): replace failing public RPC endpoints * fix(synapse-interface): distinguish RPC outages from execution errors * Publish - @synapsecns/rest-api@1.13.40 - @synapsecns/sdk-router@0.23.4 - @synapsecns/synapse-interface@0.45.1 - @synapsecns/widget-example@0.2.6 - @synapsecns/widget@0.11.6 * Add Syn bridging routes and state-managed bridge support (#4135) * feat(sdk-router): add SYN bridging to HyperEVM and HyperCore * fix(synapse-interface): derive destinations from the selected route * feat(synapse-interface): add SYN routes with native HyperCore token IDs * fix(synapse-interface): repair Ethereum and development RPC access * Update Hyperliquid explorer links * feat(sdk-router): support SYN fallback delivery on HyperEVM * feat(synapse-interface): acknowledge inactive SYN recipients * fix(synapse-interface): track actual SYN delivery destination * refactor(sdk-router): simplify SYN delivery verification * refactor(synapse-interface): address SonarCloud findings * ci: replace deprecated SonarCloud scan actions --------- Co-authored-by: trajan0x <83933037+trajan0x@users.noreply.github.com> Co-authored-by: trajan0x <trajan0x@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Kurt Siegfried <kurt.siegfried@gmail.com> Co-authored-by: ChiTimesChi <88190723+ChiTimesChi@users.noreply.github.com> Co-authored-by: ChiTimesChi <ChiTimesChi@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4142 +/- ##
=============================================
Coverage 57.57648% 57.57648%
=============================================
Files 147 147
Lines 4217 4217
Branches 809 809
=============================================
Hits 2428 2428
Misses 1699 1699
Partials 90 90
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Deploying sanguine-fe with
|
| Latest commit: |
fc3e96f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://cc239fb2.sanguine-fe.pages.dev |
| Branch Preview URL: | https://codex-repair-fe-release-sept.sanguine-fe.pages.dev |
This branch had an error being deployed
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
Restore the ancestry lost when master was squash-merged into fe-release in #4136. This PR changes zero files and preserves the exact current master tree.
The repair commit has two parents:
3b95ecfc759ae8ed89631c8731bdd76c93235fb19fbec5c2b2c7e35223c20c390db8143321205202The squash has exactly the same tree as original master commit
f43582d09. Its changes are already present in master, so recording this historical commit as merged is safe. The later WalletConnect fix on fe-release (ad6cdc6d8) is also already present in master (795aa4f70) with the same patch ID.Required merge method and follow-up
Use Create a merge commit. Do not squash or rebase this PR: the second parent is the fix, and those methods discard it.
After this PR is merged, open the follow-up PR from
fe-releaseintomasterand merge that PR using Create a merge commit as well. This repair deliberately acknowledges only the historical squash, leaving the later FE commits available for that follow-up PR.At the current branch tips, the follow-up also has zero content changes because all FE code is already on master. Master-only QuickNode routing and published package versions remain intact. New FE changes added before the follow-up will need a fresh merge check.
Verification
0a194bd48) into current master produces conflicts in 11 files.9a27be35531b9e6a023153ab9ba9907e6a43d092.git diff 3b95ecfc7 HEADis empty.git merge-tree --write-tree HEAD 0a194bd48succeeds without conflicts and produces the exact same master tree.No source code changes; verification checks Git ancestry and tree contents.