Skip to content

ci(maestro): bump WalletConnect/actions for redesigned /collect IC form#556

Draft
ignaciosantise wants to merge 1 commit into
mainfrom
ci/bump-actions-collect-ic-redesign
Draft

ci(maestro): bump WalletConnect/actions for redesigned /collect IC form#556
ignaciosantise wants to merge 1 commit into
mainfrom
ci/bump-actions-collect-ic-redesign

Conversation

@ignaciosantise

Copy link
Copy Markdown
Collaborator

Bump WalletConnect/actions maestro refs for the redesigned /collect IC form

WalletConnect/buyer-experience PR #914 redesigns the hosted KYC webview (the /collect route the sample wallet opens in a WebView). The native Maestro pay flows drive that webview by visible text/testIDs, so they were updated in WalletConnect/actions#106 (submit button "Add" → "Confirm", "Confirm your details" dialog removed, inline consent-checkbox).

This PR bumps every pinned WalletConnect/actions/maestro/* ref (pay-tests / setup / permit2-reset) to the new flow commit so the KYC flows match the redesigned form.

⚠️ Provisional SHA — do not merge yet

The ref is pinned to the branch tip of WalletConnect/actions#106 (a6436df), not a merged-master SHA. Before this PR leaves draft:

  1. fix(maestro/pay-tests): adapt KYC flows to redesigned /collect inline IC form WalletConnect/actions#106 must merge to master — then re-pin to the merged-master SHA (git rev-parse origin/master).
  2. buyer-experience #914 must be deployed to the env this wallet's /collect webview loads (prod/staging). The new steps fail against the old form and vice-versa — there is an unavoidable mutually-exclusive window; coordinate so a pay-tagged Maestro run doesn't start mid-window.

Sequencing

  1. Merge & deploy buyer-experience #914 → verify new /collect form is live.
  2. Merge fix(maestro/pay-tests): adapt KYC flows to redesigned /collect inline IC form WalletConnect/actions#106.
  3. Re-pin the SHA here to merged master, then merge this PR.
  4. Watch the first native pay Maestro run to confirm the KYC flows pass.

🤖 Generated with Claude Code

…llect IC form

Provisionally pinned to the branch tip of WalletConnect/actions#106 (KYC
/collect inline IC form redesign). Re-pin to the merged-master SHA before
merging, and only after buyer-experience #914 is deployed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 29, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
deposit-app-demo Error Error Jun 29, 2026 9:07pm
pos-demo Ready Ready Preview, Comment Jun 29, 2026 9:07pm

Request Review

@claude

claude Bot commented Jun 29, 2026

Copy link
Copy Markdown

Claude finished @ignaciosantise's task in 1m 9s —— View job


Review

  • Gather context
  • Read changed file
  • Run breaking changes subagent
  • Run data classification subagent
  • Post review findings

✅ No issues found

The diff bumps three pinned SHA refs (pay-tests, setup, permit2-reset) inside the composite action to a6436dfbb6404e7c086b24054821eb8efcc41b22. No inputs, outputs, or step IDs changed — consumer interface is intact.

The provisional-SHA situation (branch tip vs. merged-master) is correctly called out in inline comments on lines 433, 436, and 605 and is the central sequencing concern in the PR description. No additional flags from the breaking-changes or data-classification checks.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant