ci: run e2e tests with canary versions on manual comment of /canary-ci run

[tylersayshi]

Update react versions to canary when running /canary-ci run

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
waku	✅ Ready (Inspect)	Visit Preview	Dec 9, 2024 11:19pm

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[tylersayshi]

@dai-shi is it ok to always use only canary versions when running the e2e tests on main or do we need to re-run with the versions we use in PRs as well?

Currently this just updates all to canary when on main, but I am open to reconsidering

[dai-shi]

Yeah, that's concerning.
On second thought, can we trigger the CI on canary manually in a PR?
It can be a separate workflow besides ci.yaml.
Something like this: https://github.com/pmndrs/jotai/blob/d2a42f785b9803764b97fbb0ccd349d2d99069e9/.github/workflows/ecosystem-ci.yml#L10

and this: https://docs.github.com/en/actions/sharing-automations/reusing-workflows#calling-a-reusable-workflow

[tylersayshi]

/canary-ci run

[tylersayshi]

/canary-ci run

@dai-shi is this how this is supposed to work? I think I am missing something for how the jotai ecosystem ci is supposed to work, but I think I mirrored the changes here for it to work the same?

[dai-shi]

is this how this is supposed to work?

I tried it in jotai before, but it had to be merged into main.

[tylersayshi]

closing in favor of #1057