Test the latest published Next.js canary nightly
Add a second nightly Adapter API deploy-suite run for the latest published next@canary, alongside the existing supported-release run. Resolve npm's canary version once, pin every shard to the corresponding Git tag's commit, and include the version and SHA in the plan summary. Failed lookups stop planning.
Each run covers the full upstream manifest on the local Cloudflare and Node.js targets, with 64 shards per target. Runs keep separate artifacts and reports, and Canary failures retain version-specific judging. Production runtime code is unchanged.
Validation: all 41 tests in tools/deploy-tests/test/workflow-security.test.ts pass, including both schedules, lightweight and annotated tags, and registry/tag resolution failures. Changed-file ESLint, formatting, and git diff --check pass. Full repository checks are left to CI.
References: Next.js Canary releases, GitHub scheduled events.
Summary by cubic
Adds a second nightly Adapter API deploy-suite run testing the latest published next@canary, next to the existing supported-release run.
- The canary run at 18:23 UTC resolves npm's dist-tag once, resolves that version's exact Git tag to a commit SHA, and pins every shard to that commit.
- A failed registry or tag lookup, an invalid version, or an unrecognized schedule stops the plan without outputs.
- Canary runs keep separate results and summaries, and canary failures are judged against their own version and commit instead of the supported release's reviewed exceptions.