release: sync stable to main for version 13.33.0#43087
Open
metamaskbot wants to merge 17 commits into
Open
Conversation
Resolves conflicts for the stable→release/13.33.0 sync (PR #42878). For all 30 conflicting paths, took release/13.33.0 ("theirs"): - ui/pages/.../perps-withdraw-info.tsx: kept release/13.33.0's percentage controls feature (#42783, hasMax + getTradeableBalance). Stable's older "Unified Account bridge" code was the 13.32.0 MVP and is intentionally superseded by the 13.33.0 UI. - package.json / yarn.lock / lavamoat policies / attribution.txt: took release/13.33.0 to preserve next-release dependency state. Stable-only patches that target deps release/13.33.0 has moved past (assets-controller@7.0.0 patch, replaced by ^8.0.1) are dropped. - app/_locales/*/messages.json (14 files): took release/13.33.0 (Crowdin batch on release is newer; verify-locales validates the result). Same pattern as the previous 13.32.0 sync (270614f). After this merge, release/13.33.0 → stable (PR #42874) is conflict-free as long as no new commits land on stable before that PR merges.
chore: sync stable into release/13.33.0
…3.33.0 (#42951) - fix: OneKey hardware wallet routing cp-13.33.0 (#42933) ## **Description** This PR adds fix for OneKey hardware wallet. ## **Changelog** <!-- If this PR is not End-User-Facing and should not show up in the CHANGELOG, you can choose to either: 1. Write `CHANGELOG entry: null` 2. Label with `no-changelog` If this PR is End-User-Facing, please write a short User-Facing description in the past tense like: `CHANGELOG entry: Added a new tab for users to see their NFTs` `CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker` (This helps the Release Engineer do their job more quickly and accurately) --> CHANGELOG entry: Fix onboarding routing for OneKey hardware wallet ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/MUL-1838 ## **Manual testing steps** 1. Create a wallet. 2. Click on the accounts list 3. Click on connect hardware wallet 4. Click on OneKey 5. Make sure that it proceeds with QR hardware wallet onboarding flow. ## **Screenshots/Recordings** ### **Before** No UI Changes, just UX. The previous flow was routing to Trezor hardware wallet onboarding. ### **After** No UI changes, just UX. Now we're routing `OneKey` to the standard QR hardware wallet onboarding flow. https://github.com/user-attachments/assets/2d2f50b7-0ab7-4c7f-9154-a30aab661afd ## **Pre-merge author checklist** - [ ] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Small UX routing fix on the hardware selection screen with an updated unit test; no auth, data, or API changes. > > **Overview** > **OneKey** on the connect-hardware wallet picker now starts the same onboarding path as **Keystone** and **Other QR wallet**, by passing `HardwareDeviceNames.qr` instead of `HardwareDeviceNames.oneKey` into `connectToHardwareWallet`. The OneKey tile, label, and test id are unchanged; only the device type used for routing is updated. The unit test is renamed and expects the QR flow. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 42046ea. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> [cc9c995](cc9c995) Co-authored-by: David Drazic <david@timechaser.org>
…g accounts in hardware wallet onboarding cp-13.33.0 (#42979) - fix: remove redundant title for selecting accounts in hardware wallet onboarding cp-13.33.0 (#42969) ## **Description** This PR removes redundant title saying "Select an account" on a screen used in hardware wallet onboarding flow. ## **Changelog** <!-- If this PR is not End-User-Facing and should not show up in the CHANGELOG, you can choose to either: 1. Write `CHANGELOG entry: null` 2. Label with `no-changelog` If this PR is End-User-Facing, please write a short User-Facing description in the past tense like: `CHANGELOG entry: Added a new tab for users to see their NFTs` `CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker` (This helps the Release Engineer do their job more quickly and accurately) --> CHANGELOG entry: Remove redundant title for selecting accounts in hardware wallet onboarding ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/MUL-1837 ## **Manual testing steps** 1. Connect any hardware wallet 2. Get to the last step of account creation 3. Make sure that there is only one title saying "Select an account" ## **Screenshots/Recordings** ### **Before** ***Ledger*** <img width="963" height="668" alt="Screenshot 2026-05-27 at 12 20 28" src="https://github.com/user-attachments/assets/38e14656-e891-4ed6-9434-6954c2e67c23" /> ***QR*** <img width="3456" height="1802" alt="image" src="https://github.com/user-attachments/assets/f587702a-597f-4178-967e-5032b175093d" /> ### **After** ***Ledger*** <img width="963" height="668" alt="Screenshot 2026-05-27 at 12 21 39" src="https://github.com/user-attachments/assets/08673904-bfb5-4dd6-b54a-527fc10a7792" /> ***QR*** <img width="963" height="665" alt="Screenshot 2026-05-27 at 12 23 12" src="https://github.com/user-attachments/assets/aebb776d-7b8d-4601-bddc-cacc0970b4ec" /> ## **Pre-merge author checklist** - [ ] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Copy-only UI change in the hardware connect account list header with no logic or data handling impact. > > **Overview** > Removes a **second** “Select an account” heading from the hardware wallet account picker header in `account-list.tsx`, so the screen shows that title only once at the top. > > When HD path selection is shown (Ledger, Lattice, Trezor, OneKey), the flow now goes from that single account title into “Select HD path” and the account list, without repeating the same heading. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit ddfe8f1. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> [44b4dbd](44b4dbd) Co-authored-by: David Drazic <david@timechaser.org>
…ng (cp-13.33.0) (#43021) - fix: Prevent Snaps origins from connecting (cp-13.33.0) (#43017) <!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** Some small Snaps fixes. More details in JIRA ticket below. https://consensyssoftware.atlassian.net/browse/WPC-1012 ## **Changelog** <!-- If this PR is not End-User-Facing and should not show up in the CHANGELOG, you can choose to either: 1. Write `CHANGELOG entry: null` 2. Label with `no-changelog` If this PR is End-User-Facing, please write a short User-Facing description in the past tense like: `CHANGELOG entry: Added a new tab for users to see their NFTs` `CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker` (This helps the Release Engineer do their job more quickly and accurately) --> CHANGELOG entry: ## **Related issues** Fixes: ## **Manual testing steps** 1. Go to this page... 2. 3. ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [ ] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Changes externally_connectable handling and Snaps execution environment versions; security-relevant connection gating but narrow hostname list and dependency bump only. > > **Overview** > **Blocks Snaps execution origins from connecting** via `externally_connectable` by disconnecting ports whose sender hostname is `execution.metamask.io` or `execution.consensys.io` (WPC-1012). Port blocking for `trezor-connect` is unchanged in behavior but moved to shared `BLOCKED_PORTS` in `app/scripts/constants/background.ts`. > > **Snaps iframe/runtime bump:** all main build flavors point `IFRAME_EXECUTION_ENVIRONMENT_URL` at **11.1.1** (was 11.0.1), with `@metamask/snaps-execution-environments` **^11.1.1** and `@metamask/snaps-utils` **^12.2.1** in `package.json` / lockfile. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 489ce0d. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> [d49f6f9](d49f6f9) --------- Co-authored-by: Maarten Zuidhoorn <maarten@zuidhoorn.com> Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
…d calls (#42994) - fix: prevent assets controller background calls cp-13.33.0 (#42990) <!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> Patches from MetaMask/core#8914 Ensures that AssetsController does not make any calls in the background. ## **Changelog** <!-- If this PR is not End-User-Facing and should not show up in the CHANGELOG, you can choose to either: 1. Write `CHANGELOG entry: null` 2. Label with `no-changelog` If this PR is End-User-Facing, please write a short User-Facing description in the past tense like: `CHANGELOG entry: Added a new tab for users to see their NFTs` `CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker` (This helps the Release Engineer do their job more quickly and accurately) --> CHANGELOG entry: Fixed a bug that was causing some calls to services when the app is not open ## **Related issues** Fixes: #42991 ## **Manual testing steps** Open MetaMask without putting the password Open Network Tab Request to price-api happens before the password is added ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> https://github.com/user-attachments/assets/6faa5079-f72b-4f2b-ae56-63d49cb0bdbd ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [X] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [X] I've completed the PR template to the best of my ability - [X] I’ve included tests if applicable - [X] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [X] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Changes when background asset/RPC polling runs and patches upstream controller behavior; mis-timed isUiOpen could affect balances when the popup is closed or delay updates when open. > > **Overview** > Stops **AssetsController** from hitting balance/price/detection services while the extension UI is closed by wiring `isEnabled` to **`ClientController.state.isUiOpen`** (via `getMessengerClient`) instead of a hard-coded disabled flag. > > A **Yarn patch** on `@metamask/assets-controller@8.0.1` stores `isEnabled` as a callable (not a one-shot boolean), removes the constructor early-return when disabled, and evaluates `.call(this)` when handling active-chain updates so the gate stays dynamic. > > **`assets-controller-init`** replaces 24-hour poll intervals with **30s** balance/staked, **180s** detection/price when the controller is active. Tests cover the new `isEnabled` behavior and interval expectations. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 98e753e. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> [8164431](8164431) --------- Co-authored-by: Bernardo Garces Chapero <bernardo.chapero@consensys.net> Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
….33.0 (#43035) - fix: addToken uses flag internally cp-13.33.0 (#43030) <!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> Ensure the correct controller is called when an action to `addToken` is dispatched. ## **Changelog** <!-- If this PR is not End-User-Facing and should not show up in the CHANGELOG, you can choose to either: 1. Write `CHANGELOG entry: null` 2. Label with `no-changelog` If this PR is End-User-Facing, please write a short User-Facing description in the past tense like: `CHANGELOG entry: Added a new tab for users to see their NFTs` `CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker` (This helps the Release Engineer do their job more quickly and accurately) --> CHANGELOG entry: Fixed issue with MM Pay not working with the new AssetsController ## **Related issues** Fixes: #43031 ## **Manual testing steps** 1. Don't have mUSD in your token list 2. Start a mUSD conversion ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> https://github.com/user-attachments/assets/90bb2fc6-3edf-4c94-a2d0-9ac7594ca5b5 ### **After** <!-- [screenshots/recordings] --> https://github.com/user-attachments/assets/0b6e0ca9-04e2-4882-9a72-4f6033baef74 ## **Pre-merge author checklist** - [X] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [X] I've completed the PR template to the best of my ability - [X] I’ve included tests if applicable - [X] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [X] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Changes token-import behavior behind a feature flag; wrong gating could break MM Pay or legacy token lists, but scope is limited to `addToken` and is covered by new tests. > > **Overview** > The public **`addToken`** API on `MetaMaskController` no longer always forwards to **`TokensController.addToken`**. It now branches on **`#isAssetsUnifyStateEnabled()`**: with unified assets on, it resolves the selected account and chain from **`networkClientId`**, builds an **`assetId`** via **`toAssetId`**, and registers the token through **`AssetsController.addCustomAsset`** (optional **`iconUrl`** from **`image`**); otherwise it keeps the legacy **`tokensController.addToken`** path. Missing **`chainId`** / **`assetId`** now throws instead of silently mis-registering. > > Tests cover delegation when unify is off, the unified **`addCustomAsset`** path (with and without image), and the error when **`assetId`** cannot be built, using real remote-feature-flag gating instead of the global Jest mock. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit eba01c8. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> [3b7a78e](3b7a78e) Co-authored-by: Bernardo Garces Chapero <bernardo.chapero@consensys.net>
chore: sync stable into release/13.33.0
… to `1.25.6` (#43038) - chore: bump `@metamask/tron-wallet-snap` to `1.25.6` (#42701) <!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> This PR bumps @metamask/tron-wallet-snap from `^1.25.3` to `^1.25.6`. The main purpose of this update is to pull in the latest Tron snap validation fixes, in particular a mechanism to refresh stale or invalid `expiration`, `ref_block_bytes` and `ref_block_hash` before signing in both send/broadcast paths. Preview package: - `@metamask-previews/tron-wallet-snap@1.25.3-preview-995ddc5` Release: - `@metamask-previews/tron-wallet-snap@^1.25.6` Upstream PR: - MetaMask/snap-tron-wallet#305 Updated following `e2e` test files to adapt new logic for refresh transaction expiration - `test/e2e/flask/tron-connect/mocks/trongrid.ts` - `test/e2e/flask/tron-connect/common-tron.ts` - `test/e2e/tests/tron/mocks/common-tron.ts` - `test/e2e/flask/tron-connect/signAndSendTrx.spec.ts` - `test/e2e/flask/tron-connect/signAndSendUsdt.spec.ts` ## **Changelog** <!-- If this PR is not End-User-Facing and should not show up in the CHANGELOG, you can choose to either: 1. Write `CHANGELOG entry: null` 2. Label with `no-changelog` If this PR is End-User-Facing, please write a short User-Facing description in the past tense like: `CHANGELOG entry: Added a new tab for users to see their NFTs` `CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker` (This helps the Release Engineer do their job more quickly and accurately) --> CHANGELOG entry: bump the `@metamask/tron-wallet-snap` to `^1.25.6` ## **Related issues** n/a ## **Manual testing steps** 1. Go to this page... 2. 3. ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [X] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [X] I've completed the PR template to the best of my ability - [X] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Ships a snap version that changes pre-sign transaction validation/refresh on Tron send paths; risk is mitigated by e2e mock updates but still affects real signing behavior. > > **Overview** > Bumps **`@metamask/tron-wallet-snap`** from `^1.25.3` to **`^1.25.6`** (and lockfile) so the extension picks up upstream fixes that **refresh stale Tron transaction fields** (`expiration`, `ref_block_bytes`, `ref_block_hash`) before sign/broadcast. > > E2E mocks are expanded so tests match that behavior: shared block payloads, new handlers for **`getnowblock`**, **`getblockbynum`**, and Infura **`getnowblock`**; broadcast mocks now return success instead of expiration errors; swap/bridge fixture data uses **future-dated** expirations and aligned ref-block values for stable CI. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit a92c9de. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: gabrieledm <gabriele.delmonte@proton.me> Co-authored-by: Gabriele Del Monte <37625739+gabrieledm@users.noreply.github.com> Co-authored-by: Maxime OUAIRY <maxime.ouairy-ext@consensys.net> [4d85bd5](4d85bd5) --------- Co-authored-by: Ulisses Ferreira <ulisses@hey.com> Co-authored-by: gabrieledm <gabriele.delmonte@proton.me> Co-authored-by: Gabriele Del Monte <37625739+gabrieledm@users.noreply.github.com> Co-authored-by: Maxime OUAIRY <maxime.ouairy-ext@consensys.net> Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
This PR updates the change log for 13.33.0. (Hotfix - no test plan generated.) --------- Co-authored-by: metamaskbot <metamaskbot@users.noreply.github.com> Co-authored-by: Tatiana Bobritsky <tatiana.bobritsky@consensys.net>
release: 13.33.0
Contributor
|
CLA Signature Action: Thank you for your submission, we really appreciate it. We ask that you all read and sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just by adding a comment to this pull request with this exact sentence:
By commenting with the above message you are agreeing to the terms of the CLA. Your account will be recorded as agreeing to our CLA so you don't need to sign it again for future contributions to this repository. 2 out of 3 committers have signed the CLA. |
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.
This PR syncs the stable branch to main for version 13.33.0.
Synchronization Process:
File Preservation:
Preserves specific files from the stable branch:
Indicates the next version candidate of main to 13.33.0