Skip to content

[pull] canary from vercel:canary #89

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.

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

Merged
merged 3 commits into from
May 3, 2025
Merged

[pull] canary from vercel:canary #89

merged 3 commits into from
May 3, 2025

Conversation

pull[bot]
Copy link

@pull pull bot commented May 3, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

ijjk and others added 3 commits May 2, 2025 14:33
This attempts to stabilize the back-forward-cache test assertions by
adding retry to the initial button incrementing as I have a theory this
was attempting to click before the event listeners were attached causing
the clicks to be missed which makes the successive test cases fail.

x-ref:
https://github.com/vercel/next.js/actions/runs/14766354734/job/41458564789#step:33:481
x-ref:
https://github.com/vercel/next.js/actions/runs/14766354734/job/41459734942#step:33:191
This aims to avoid running the `build_and_deploy` workflow twice when
pushed to the main Next.js repo and also opened as a PR.

Follow-up to #78737

Validated against:
https://github.com/vercel/next.js/actions/runs/14804173232/job/41569421246?pr=78795
@pull pull bot added the ⤵️ pull label May 3, 2025
@pull pull bot merged commit f62a135 into code:canary May 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants