Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): bump @metamask/ppom-validator to 0.35.1 #11779

Closed
wants to merge 3 commits into from
Closed

chore(deps): bump @metamask/ppom-validator to 0.35.1 #11779

wants to merge 3 commits into from
+21 −92

Conversation

mikesposito
Copy link
Member

@mikesposito mikesposito commented Oct 14, 2024 •
edited by cryptodev-2s
Loading

Description

This PR updates @metamask/ppom-validator to 0.35.1

Related issues

Fixes: #11134

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Before

After

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.

@socket-security Socket Security
Copy link

socket-security bot commented Oct 14, 2024 •
edited
Loading

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@metamask/[email protected] None 0 122 kB metamaskbot

🚮 Removed packages: npm/@metamask/[email protected]

View full report↗︎

@cryptodev-2s cryptodev-2s force-pushed the mikesposito/bump-ppom-validator branch from 50ef822 to 5702bf5 Compare October 24, 2024 15:26
@cryptodev-2s cryptodev-2s changed the title chore(deps): bump @metamask/ppom-validator to 0.35.0 chore(deps): bump @metamask/ppom-validator to 0.35.1 Oct 24, 2024
@github-actions GitHub Actions
Copy link
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.

@cryptodev-2s cryptodev-2s added the Run Smoke E2E Triggers smoke e2e on Bitrise label Oct 24, 2024
@github-actions GitHub Actions
Copy link
Contributor

https://bitrise.io/ Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 5702bf5
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/12f4c73a-0ff6-4b60-9b18-bc0986f2fd5c

Note

  • This comment will auto-update when build completes
  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

@cryptodev-2s cryptodev-2s added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Oct 24, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Oct 24, 2024 •
edited by metamaskbot
Loading

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 5239c74
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f1a77244-3ce3-4a7f-91bd-20baec3d1fef

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

  • Check the documentation if you have any doubts on how to understand the failure on bitrise

@mikesposito
Copy link
Member Author

Closing in favor of #11114

@github-actions github-actions bot locked and limited conversation to collaborators Oct 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
Run Smoke E2E Triggers smoke e2e on Bitrise team-wallet-framework
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

chore(deps): Bump @metamask/ppom-validator from 0.32.0 to 0.35.1
2 participants
@mikesposito @cryptodev-2s