fix: publish the 7.x @decocms/tanstack and @decocms/nextjs on latest-7

Merged
TL
19h ago
+11-10

Why

From 8.3.0, main publishes @decocms/tanstack and @decocms/nextjs v8 on npm's latest (decocms/blocks#699's release mechanics). Today this branch publishes both with --tag latest, so the first 7.x release after 8.3.0 would take latest back to a 7.x version and new sites would install v7.

What changes

  • .releaserc.json: tanstack and nextjs join blocks and the shared apps in V7_CHANNEL_PKGS, so 7.x releases publish them on latest-7. The other v7-only packages (blocks-admin, blocks-cli, eitri, the v7-only apps) keep latest.
  • release.yml's comment and the install docs (README.md, packages/nextjs/README.md) say @decocms/tanstack@latest-7 / @decocms/nextjs@latest-7.

Rendered publish step in dry-run mode (DRY_RUN=true): @decocms/tanstack@7.79.7 --tag latest-7, @decocms/nextjs@7.79.7 --tag latest-7, @decocms/blocks-admin@7.79.7 --tag latest, and the rest as before.

Order

Merge this before the v8 stack lands on main, or at the latest before any other 7.x release after 8.3.0. Merging it releases 7.79.7 of the 7.x packages (a fix:), which puts latest-7 on 7.79.7 for both bindings; the npm dist-tag add … latest-7 commands in the v8 release PR are then already done (don't move latest-7 back to 7.79.6).

Claude-Session: https://claude.ai/code/session_01WNwbSEePYNcY5YCgqZURig

🤖 Generated with Claude Code

Summary by cubic

Stops the 7.x line from republishing @decocms/tanstack and @decocms/nextjs on npm's latest, which has carried 8.x since 8.3.0. Both bindings now publish on the latest-7 dist-tag alongside @decocms/blocks and the apps v8 also ships, so the first 7.x release won't pull latest back to a 7.x version.

Rollout

  • Merge before any other 7.x release after 8.3.0; the publish itself moves latest-7 to 7.79.7 for both bindings, which covers the npm dist-tag add steps in the v8 release.

Documentation

  • Install commands in README.md and packages/nextjs/README.md now use @latest-7 for both bindings.