Open
Conversation
fix: codex config relative path to AGENTS.md Codex resolves model_instructions_file relative to .codex/ dir, so "AGENTS.md" was looking for .codex/AGENTS.md instead of repo root. Co-authored-by: gomes-bot <[email protected]> Co-authored-by: Claude Opus 4.6 <[email protected]>
The native QR scanner handler ships in mobile app v3.7.2 (mobile-app PR #156), but the version gate was set to 3.4.0. This caused mobile apps v3.4.0–3.7.1 to incorrectly attempt native scanning, resulting in a 60-second spinner timeout with no way to scan. Co-authored-by: Claude Opus 4.6 <[email protected]>
) * fix: prevent duplicate private sync pr in release script merged_untagged case was creating a private sync PR without checking if one already existed, unlike tagged_private_stale which had the guard. Co-Authored-By: Claude Sonnet 4.6 <[email protected]> * fix: prevent duplicate private sync pr in release script tagged_private_stale case was creating a private sync PR even when private was already content-identical to main (SHA mismatch due to propagation delay after a sync PR merges). Added a content diff check to bail early in that case. Same guard applied to the hotfix path. The merged_untagged case also gets the open-PR guard for belt-and-suspenders. Co-Authored-By: Claude Sonnet 4.6 <[email protected]> * fix: idle prereleaseMerged content diff + tagged_private_stale backmerge auto-merge - idle case: use git diff content check instead of SHA equality for prereleaseMerged - squash merges diverge SHAs even when content matches - tagged_private_stale (regular + hotfix): set auto-merge with merge commit strategy on backmerge PR so it lands without manual intervention Co-Authored-By: Claude Sonnet 4.6 <[email protected]> * fix: coderabbitai review - prereleaseMerged ahead-check + no early break in tagged_private_stale - idle: replace SHA/content-diff prereleaseMerged with commit-ahead check (origin/main..origin/release) - prevents false positive when release is *behind* main (e.g. post-hotfix), which would have routed into release PR path with 0 commits - tagged_private_stale (regular + hotfix): remove early break when private is content-synced - script must still evaluate backmerge PR creation even when private sync is a no-op Co-Authored-By: Claude Sonnet 4.6 <[email protected]> * fix: prettier formatting in release script * fix: enable auto-merge on existing backmerge PRs during reruns Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * fix: lint --------- Co-authored-by: Claude Sonnet 4.6 <[email protected]> Co-authored-by: gomes-bot <[email protected]>
* chore: update near affiliate address * docs: update qabot skill for agent-browser 0.20.x features Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> --------- Co-authored-by: Apotheosis <[email protected]> Co-authored-by: gomes-bot <[email protected]> Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
4 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.
Description
v1.1018.0 release.
Production changes - testing required
RPC fallback resilience for unchained outages (#12017)
getAccount(),broadcastTransaction(),getGasFeeData()now fall back to direct RPC when unchained returns 503connect-srcupdated for all fallback originsVITE_ETHEREUM_NODE_URL=https://httpstat.us/503), verify ETH balance loads and console shows fallback messageCustom token metadata proxy (#12040)
api.proxy.shapeshift.com- removes exposed client-side Alchemy keyVITE_ALCHEMY_POLYGON_URLand dead client-side Alchemy SDK usageAffiliate system alignment (#12150)
partnerCodeprop to swap widget,X-Partner-Codeheader support in public-apirFOX staking asset selection fix (#12175)
Yield improvements (#12174, #12176)
WalletConnect network modal (#12169)
Fixes, deps, and infra
Dev/local only - no production testing required
Release script fixes
Tooling
Risk
Medium overall - RPC fallback and custom token proxy are the biggest surface areas, both additive/fallback only with no happy-path changes.