chore: backmerge production app and landing fixes (TASK-22564) - #3258
Conversation
The March QR-launch triplet (Buenos Aires, São Paulo, Floripa) framed the homepage as a LatAm street-payments pitch. With the card live the hero returns to the global sweep the Global Cash fold already uses, and each city links to its country page through the resolved content hrefs instead of hardcoded locale paths. Drops the locale prop that only fed those paths.
Nueva York / Ciudad de México on the Spanish pages and Nova York / Madri / Cidade do México on Portuguese, matching the forms the Global Cash fold already uses. Addresses the Chip review note on #3093.
Carries the hero city change over the app-entry refactor (#3027): Hero keeps main's signature and useMigrationFlag, takes contentHrefs in place of locale.
Hero no longer takes locale; the guard added on main in d91ea7c still passed it, so the two Hero cases threw on contentHrefs.unitedStates.
LandingPageClient no longer takes locale; the Vercel build type-checks tests and failed on it. Hero reads contentHrefs now, so the guard passes the real EN map instead of an empty cast.
Static images for the launch email blast, served at peanut.me/email/. Same four assets as ui#3226 (dev), based on main so the blast can send today; back-merge covers dev.
…mation-currency fix(add-money): preserve EUR on native SEPA confirmation
…y-no-native fix(app): avoid native rebuild for app-entry QR links
Slava's catch: multi-second image loads in the launch emails. 780px + 128-color palette PNG, visually identical. Same filenames, so already-sent emails also load faster (clients fetch at open time).
the constant still held the pre-launch placeholder (2026-12-31), so the web sunset block would not fire for another three months. the pwa-sunset flag went blanket-on 2026-09-09, and the notice window is 30 days, which puts the cutover at 2026-10-09. the comparison in shouldShowSunsetBlock is `now >= cutover`, so the block starts at exactly 2026-10-09T00:00:00Z — the last full web day is 2026-10-08 UTC.
…r-date fix: set the real pwa-sunset cutover date (2026-10-09)
feat(landing): hero cities back to New York, Madrid, Mexico City (TASK-22577)
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Code-analysis diffPainscore total: 8458.28 → 8460.03 (+1.75) 🆕 New findings (33)
…and 13 more. ✅ Resolved (32)
…and 12 more. |
🧪 UI test report — ✅ all greenSuites
📊 Coverage (unit)
⏱ 10 slowest test cases
|
🖼 Visual diff — 4 screens moved6 of 144 shots changed · 138 identical · baseline
job summary · before/after/diff images — artifact Fixture screenshots, no backend. Advisory — this check never blocks a merge. Posted from the default branch by ds-shots-comment.yml; the report it renders is untrusted data. |
Bring production app and landing changes into dev while retaining dev’s newer native release flow and app-link behavior.
84771354einto dev at6c8dc75b5./homedownload-QR gateway (fix(app): avoid native rebuild for app-entry QR links #3237), and the October 9 PWA sunset date (fix: set the real pwa-sunset cutover date (2026-10-09) #3249). The native SEPA currency fix (fix(add-money): preserve EUR on native SEPA confirmation #3238) is already present in dev and remains intact./appstays outside native associations, and retain dev’s automatic OTA instructions with main’s QR-link guidance. Remove the obsolete instruction to restore/appassociations./app/*routing.Validation: typecheck passed; full unit suite passed (680 suites, 8,343 tests); focused rerun with the new cases passed (214 tests). Production build succeeded, with local Sentry upload 401 warnings. Formatting and diff checks passed.
Risk is the combination of deep-link handling from both branches. No native manifest changes, dependencies, or new architecture. No additional product or legal changes beyond the production commits.
Screenshots:⚠️ not captured for the landing-city change. Landing tests pass, but visual and native-device checks were not repeated for this backmerge.
Replaces #3256 and the older #3231. CI and Chip review are not awaited, as requested. Use a merge commit to preserve ancestry.