docs: document prerelease channel (prerelease pipeline E2E test)

[vibe-dex]

What is this Contribution About?

End-to-end test of the new prerelease pipeline (PR #1588) while shipping a real doc improvement.

Adds a README section explaining the next-branch / apps@X.Y.Z-next.N flow and how consumers opt in via an explicit version pin in deno.json. Opening this PR should trigger the new prerelease-tag-discussion job and post a "## Prerelease Tagging" bot comment with the computed patch/minor/major bases against 0.151.1. Merging would then trigger determine-prerelease-tag and ship a 0.151.2-next.1 tag + GitHub Pre-release.

Issue Link

• Issue: N/A (companion to ci: add prerelease pipeline on next branch #1588)

Loom Video

N/A — docs + CI verification.

Demonstration Link

The bot comment that appears below this PR opening IS the demonstration. After confirming it shows correct bases, merge to ship 0.151.2-next.1.

🤖 Generated with Claude Code

---

Summary by cubic

Adds a README section that documents the prerelease channel from next (apps@X.Y.Z-next.N) and how to opt in by pinning an exact tag in deno.json. Opening this PR also exercises the prerelease tagging pipeline end to end.

• Migration
  • To opt in, pin "apps/" to https://cdn.jsdelivr.net/gh/deco-cx/apps@<X.Y.Z-next.N>/ in deno.json.
  • deno task update ignores prereleases by default; only explicit -next.N pins are used.

^{Written for commit 8d8f3fb. Summary will update on new commits.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b3ff2e6a-2572-4792-87fe-ec4e3fc8b7bd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch vibe-dex/prerelease-pipeline-test

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Prerelease Tagging

Merging this PR will publish a prerelease automatically.
By default this is a Patch prerelease (0.151.2-next.N).
A maintainer can override the bump by reacting:

• 👍 Patch prerelease 0.151.2-next.N (default)
• 🎉 Minor prerelease 0.152.0-next.N
• 🚀 Major prerelease 1.0.0-next.N

.N auto-increments per base. Consumers opt in by pinning the exact tag in deno.json imports, e.g.
"apps/": "https://cdn.jsdelivr.net/gh/deco-cx/apps@0.151.2-next.1/".
The stable apps@<X.Y.Z> pin is unaffected because deno task update filters out semver prereleases by default.

[cubic-dev-ai]

No issues found across 1 file