ci: version-driven releases from deno.json

[kojiwakayama]

Summary

Replace tag-based and manual-dispatch release triggers with automatic detection from the version string in deno.json:

• X.Y.Z (clean semver) → stable release (npm latest + GitHub release + Homebrew + git tag)
• Anything else (e.g. X.Y.Z-rc) → RC release (npm rc tag + GitHub pre-release)

How it works

A new version-check job reads deno.json on every push to main and outputs is_stable. Downstream jobs branch accordingly:

Push to main
    ↓
version-check (reads deno.json)
    ↓
┌─── is_stable=false ───┐    ┌─── is_stable=true ──────┐
│  prerelease job       │    │  release job             │
│  npm publish --tag rc │    │  npm publish (latest)    │
│  GitHub pre-release   │    │  Create git tag          │
│  Server deploy        │    │  GitHub release          │
└───────────────────────┘    │  Homebrew tap update     │
                             │  Server deploy           │
                             └──────────────────────────┘

Release workflow

1. Day-to-day: deno.json has 0.1.14-rc → every merge to main publishes RC
2. Stable release: PR that changes version to 0.1.14 → merge publishes as latest
3. Next cycle: Bump to 0.1.15-rc in follow-up commit

Changes

• Removed tags: ["v*"] trigger and workflow_dispatch release input
• Added version-check job that detects RC vs stable from deno.json
• prerelease job runs only when is_stable=false
• release job runs only when is_stable=true (with environment: production approval gate)
• Stable release auto-creates git tag (with duplicate check)
• update-homebrew uses version from version-check outputs instead of git tag ref
• Removed release-tag manual dispatch job
• Simplified CI job conditions (removed tag-skip guards since tags no longer trigger workflow)

Test plan

• Verify YAML syntax is valid
• Merge with current deno.json version 0.1.13 (clean semver) → should trigger stable release path
• After release, bump to 0.1.14-rc → subsequent merges should publish RC only

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b49892cb4e

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".