feat(release): stable versions publish to latest; docs for 0.1.0 and Effect

[t3dotgg]

The release workflow sent every version to the npm dist-tag next and made a GitHub prerelease. So a v0.1.0 tag would not become what npm i tsc-rs installs. Today that is still the empty 0.0.1 placeholder.

Changes

• release.yml: a version with no prerelease part (0.1.0) publishes with --tag latest and makes a normal GitHub release. A version with a - (0.2.0-beta.1) keeps next and a prerelease. The release notes show the matching install command.
• READMEs: install with npm install -D tsc-rs, and "early release" in place of "preview". A new section covers the built-in Effect diagnostics from feat(effect): native Effect diagnostics in tsc-rs #4: they run only with the @effect/language-service plugin entry, and diagnostics default to on. The release steps in npm/README.md describe both tags.

Release dry runs on pull requests are unchanged. The publish logic runs only on a tag.

---

Made by Claude Opus 5.5 (1M context) in Claude Code, through T3 Code.

🤖 Generated with Claude Code

Note

Publish stable versions to the latest dist-tag and update docs for 0.1.0

• The release workflow now publishes versions without a prerelease component to npm's latest dist-tag, while prerelease versions still go to next. See release.yml
• GitHub releases are marked as prereleases only for prerelease versions. The generated install note recommends the unqualified package for stable versions and the next tag for prereleases
• Docs reclassify the project from preview to early release, switch install examples to the unqualified tsc-rs package, and document built-in Effect diagnostics gated behind a plugin, ported from Effect-TS/tsgo 0.46.1. See README.md and tsc-rs-readme.md
• Post-release guidance now describes promoting a prerelease to the default dist-tag after checking it
• Behavioral Change: future stable tag releases publish to latest instead of next, so existing consumers tracking next no longer receive stable versions

^{Macroscope summarized 934345c.}

Summary by CodeRabbit

• Documentation
  • Updated installation guidance to use the standard tsc-rs package.
  • Added information about Effect diagnostics, including setup requirements and current editor-feature limitations.
  • Clarified the difference between stable releases and prereleases.
• Release Process
  • Stable releases publish under latest and create standard GitHub releases; prereleases publish under next and are marked as GitHub prereleases.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Team
• Run ID: 9f48bc49-bf55-4f51-8d93-3c9ab9d31df7

📥 Commits

Reviewing files that changed from the base of the PR and between 380b9c0 and 934345c.

📒 Files selected for processing (4)

• .github/workflows/release.yml
• README.md
• npm/README.md
• npm/tsc-rs-readme.md

Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

---

Walkthrough

The release workflow now selects npm dist-tags and GitHub release types based on whether a version is stable or a prerelease. The README files describe these release steps, the early release status, and built-in Effect diagnostics.

Changes

Release publishing

Layer / File(s)	Summary
Version-based publishing .github/workflows/release.yml	The workflow publishes stable versions with the latest dist-tag and creates normal GitHub releases. It publishes prereleases with the next dist-tag and creates GitHub prereleases.
Release instructions and package status README.md, npm/README.md, npm/tsc-rs-readme.md	The README files update the release status and install command. They also document stable and prerelease tags and npm publishing steps.

Effect diagnostics documentation

Layer / File(s)	Summary
Effect diagnostic documentation README.md, npm/tsc-rs-readme.md	The README files describe the plugin configuration, diagnostic integration and source, and editor features that are not ported.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~12 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 93434

Stable and prerelease publishing behavior is consistent with the release instructions, and the Effect diagnostic documentation matches the implementation. No actionable merge-blocking issue was found.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the stable-release publishing change and the related documentation updates for 0.1.0 and Effect.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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