From 8d8f3fb4f8730cf6e9a828786f7b7b43092e934a Mon Sep 17 00:00:00 2001 From: Fernando Frizzatti Date: Thu, 14 May 2026 18:10:42 -0300 Subject: [PATCH] docs: document prerelease channel Adds a README section explaining the `next` branch / `*-next.N` tag flow and how consumers opt in via explicit version pin. Co-Authored-By: Claude Opus 4.7 (1M context) --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index ab33a74bf..ef7747214 100644 --- a/README.md +++ b/README.md @@ -21,6 +21,16 @@ Open this repo in an AI Editor and use [NewAppPrompt.md](NewAppPrompt.md) as pro --- +## Pre-release channel + +Stable releases ship from `main` (`apps@X.Y.Z`). Pre-releases ship from the `next` branch as `apps@X.Y.Z-next.N` and let you opt-in to in-progress changes. Pin an exact tag: + +```jsonc +"apps/": "https://cdn.jsdelivr.net/gh/deco-cx/apps@/" +``` + +`deno task update` filters out semver prereleases by default, so sites stay on stable unless you explicitly pin a `-next.N` version. + ## Debugging HTTP Requests To enable verbose HTTP request debugging logs, set the environment variable `DEBUG_HTTP` to `true` when running this repo: