Skip to content

fix: cherry-pick (#8742)#8765

Merged
sethkfman merged 1 commit into
release/7.17.0from
cherrypick-2148
Feb 29, 2024
Merged

fix: cherry-pick (#8742)#8765
sethkfman merged 1 commit into
release/7.17.0from
cherrypick-2148

Conversation

@blackdevelopa

@blackdevelopa blackdevelopa commented Feb 28, 2024

Copy link
Copy Markdown
Contributor

Cherry-pick fix for #8742 on version 7.17.0.

<!--
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?
-->

Context:
https://consensys.slack.com/archives/C05HZHDS89Z/p1708946195217929
Pass origin as `metamask` for ppom validate request

Fixes:

1. Go to this page...
2.
3.

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

<!-- [screenshots/recordings] -->

<!-- [screenshots/recordings] -->

- [ ] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've clearly explained what problem this PR is solving and how it
is solved.
- [ ] I've linked related issues
- [ ] I've included manual testing steps
- [ ] I've included screenshots/recordings if applicable
- [ ] 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-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.
- [ ] I’ve properly set the pull request status:
  - [ ] In case it's not yet "ready for review", I've set it to "draft".
- [ ] In case it's "ready for review", I've changed it from "draft" to
"non-draft".

- [ ] 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.
@blackdevelopa blackdevelopa requested a review from a team as a code owner February 28, 2024 10:28
@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.

@blackdevelopa blackdevelopa added the team-confirmations-secure-ux-PR PR from the confirmations team label Feb 28, 2024
@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (release/7.17.0@10aaa64). Click here to learn what that means.

Additional details and impacted files
@@                Coverage Diff                @@
##             release/7.17.0    #8765   +/-   ##
=================================================
  Coverage                  ?   41.10%           
=================================================
  Files                     ?     1248           
  Lines                     ?    30417           
  Branches                  ?     2969           
=================================================
  Hits                      ?    12504           
  Misses                    ?    17165           
  Partials                  ?      748           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@blackdevelopa blackdevelopa changed the title fix: cherry pick 2148 fix: cherry pick 8742 Feb 28, 2024
@blackdevelopa blackdevelopa changed the title fix: cherry pick 8742 fix: cherry pick (#8742) Feb 28, 2024
@blackdevelopa blackdevelopa changed the title fix: cherry pick (#8742) fix: cherry-pick (#8742) Feb 28, 2024
@metamaskbot metamaskbot added the INVALID-PR-TEMPLATE PR's body doesn't match template label Feb 28, 2024
@github-actions

Copy link
Copy Markdown
Contributor

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c7420a01-d581-4dbf-a6ca-6ad4d71f398f
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

@sethkfman sethkfman added the regression-RC DEPRECATED: Please use "regresssion-RC-x.y.z" label instead label Feb 28, 2024

@sethkfman sethkfman 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.

LGTM

@sethkfman sethkfman merged commit 9c11aac into release/7.17.0 Feb 29, 2024
@sethkfman sethkfman deleted the cherrypick-2148 branch February 29, 2024 00:48
@github-actions github-actions Bot locked and limited conversation to collaborators Feb 29, 2024
@metamaskbot metamaskbot added the release-7.17.0 Issue or pull request that will be included in release 7.17.0 label Feb 29, 2024
@metamaskbot

Copy link
Copy Markdown
Collaborator

No release label on PR. Adding release label release-7.17.0 on PR, as PR was cherry-picked in branch 7.17.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

INVALID-PR-TEMPLATE PR's body doesn't match template regression-RC DEPRECATED: Please use "regresssion-RC-x.y.z" label instead release-7.17.0 Issue or pull request that will be included in release 7.17.0 team-confirmations-secure-ux-PR PR from the confirmations team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants