Skip to content

release: release-changelog/7.68.3#27513

Merged
chloeYue merged 3 commits into
release/7.68.3from
release-changelog/7.68.3
Mar 17, 2026
Merged

release: release-changelog/7.68.3#27513
chloeYue merged 3 commits into
release/7.68.3from
release-changelog/7.68.3

Conversation

@chloeYue

@chloeYue chloeYue commented Mar 17, 2026

Copy link
Copy Markdown
Contributor

This PR updates the change log for 7.68.3. (Hotfix - no test plan generated.)

Description

Adds a new 7.68.3 section to CHANGELOG.md documenting two hotfixes:

Updates the changelog reference links so Unreleased now compares from v7.68.3 and includes a new 7.68.3 compare link.

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

N/A - changelog only

Pre-merge author checklist

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.

Made with Cursor

Made with Cursor


Note

Low Risk
Changelog-only update with no runtime code changes; risk is limited to potential version/compare-link inaccuracies in release notes.

Overview
Adds a new 7.68.3 section to CHANGELOG.md documenting two hotfixes (seedless onboarding vault decryption crash handling and OTA env var build-flag update).

Updates the version reference links by introducing a new [7.68.3] compare link.

Written by Cursor Bugbot for commit 2bbdafb. This will update automatically on new commits. Configure here.

@github-actions

Copy link
Copy Markdown
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@metamaskbot metamaskbot added team-qa QA team INVALID-PR-TEMPLATE PR's body doesn't match template labels Mar 17, 2026
@chloeYue chloeYue force-pushed the release-changelog/7.68.3 branch from b011f24 to a9e3d28 Compare March 17, 2026 09:38
Comment thread CHANGELOG.md Outdated

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Comment thread CHANGELOG.md Outdated

[Unreleased]: https://github.com/MetaMask/metamask-mobile/compare/v7.69.0...HEAD
[Unreleased]: https://github.com/MetaMask/metamask-mobile/compare/v7.68.3...HEAD
[7.68.3]: https://github.com/MetaMask/metamask-mobile/compare/v7.68.2...v7.68.3

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

v7.69.0 and v7.68.3 share identical compare base

Low Severity

Both [7.68.3] and [7.69.0] compare links use v7.68.2 as the base tag, meaning their diffs overlap. If v7.68.3 was branched off v7.68.2, and v7.69.0 includes those hotfix changes, the [7.69.0] link likely needs to compare from v7.68.3 instead of v7.68.2 to avoid showing duplicate commits in both diffs.

Fix in Cursor Fix in Web

@github-actions

Copy link
Copy Markdown
Contributor

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - base branch is not main (base: release/7.68.3)

All E2E tests pre-selected.

View GitHub Actions results

@chloeYue chloeYue merged commit adfa229 into release/7.68.3 Mar 17, 2026
34 of 36 checks passed
@chloeYue chloeYue deleted the release-changelog/7.68.3 branch March 17, 2026 09:52
@github-actions github-actions Bot locked and limited conversation to collaborators Mar 17, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants