Canary versions after recent backports targeting wrong version

[darthmaim]

Link to the code that reproduces this issue

https://github.com/darthmaim-reproductions/vercel-next.js-74139

To Reproduce

1. Init a new Next.js app using npx create-next-app@latest
2. Try to upgrade to canary using npx @next/codemod@canary upgrade canary

Current vs. Expected behavior

This currently fails with this error:

✓ Current Next.js version is higher than the target version "v15.1.1-canary.13".

The recent canary versions were released as 15.1.1-canary.X even though 15.1.1 (and just recently even 15.1.2) were released as backports, so the canary versions should have been bumped to 15.1.2 (and now 15.1.3 for the next upcoming canaries).

Provide environment information

Node.js v22.5.1

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Tue Nov 5 00:21:55 UTC 2024
  Available memory (MB): 15953
  Available CPU cores: 8
Binaries:
  Node: 22.5.1
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.1.2 // Latest available version is detected (15.1.2).
  eslint-config-next: 15.1.2
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Developer Experience

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I'm not sure how exactly the release process works, but part of releasing a backport as latest version should be bumping the next canaries version.