ci: skip releases from dormant next

[raviships]

After stable promotion and a forward merge from main, next can intentionally have no .changeset/pre.json until the following major prerelease cycle starts. The release guard currently fails on these pushes with a missing-file error (runs 37181102536 and 37182129354).

Automatic pushes to dormant next now succeed with an explanatory log and job summary, and explicitly skip the entire Changesets version/publish action. Manual release dispatches on dormant next fail with instructions to enter prerelease mode, commit the state, and push. Existing JSON, mode, tag, and branch validation remains in place.

The diff changes only .github/workflows/release.yml and RELEASING.md (21 added lines). It adds no tests, test infrastructure, package scripts, dependencies, or CI configuration. No changeset is needed for internal release tooling.

Validation: executed the actual workflow Bash guard in temporary directories for 11 manual cases covering dormant push/manual behavior, stable main, active next/RC, malformed JSON, unsupported tags/modes, and unsupported branches. Verified that the whole Changesets action requires the guard's positive output. Formatting, dependency policy, and git diff --check passed after the revision; the existing repository CI suite runs on the updated commit.

Targets main per RELEASING.md's release-infrastructure policy. After merge, forward-merge main into next to apply the fix there.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
edgestore-docs	Ready	Preview	Oct 4, 2026 1:17pm UTC
example-access-control	Ready	Preview	Oct 4, 2026 1:17pm UTC
example-components	Ready	Preview	Oct 4, 2026 1:17pm UTC

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-04T13:19:05.789301Z	e666cfe	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[raviships]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: e666cfee29

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".