docs: document release pathway + guard unpublished channels in AGENTS.md#1108
Conversation
AGENTS.md gains a Releases-and-install-docs section (its only persistent context lacked one): releases are automated after merge (no manual tag/twine/gh release), and install docs must match README/SKILL/PYPI_README (source checkout = full env + agent default; `pip install veralang` = toolchain only; never `pip install vera`). Both AGENTS.md and CLAUDE.md now forbid documenting a distribution channel as available before it's live — the VS Code Marketplace extension is still blocked (#1106). Regenerates docs/llms-full.txt. Co-Authored-By: Claude <noreply@anthropic.invalid>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 13 minutes Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1108 +/- ##
=======================================
Coverage 93.72% 93.72%
=======================================
Files 96 96
Lines 32708 32708
Branches 456 456
=======================================
Hits 30654 30654
Misses 2041 2041
Partials 13 13
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
@coderabbitai full review |
✅ Action performedFull review finished. You're currently rate limited under our Fair Usage Limits Policy. Your recent PR review activity is in the 95th percentile or higher among CodeRabbit users, so adaptive limits apply. Your next review will be available in 13 minutes. |
What
Adds a Releases and install docs section to
AGENTS.mdand an unpublished-channel guard toCLAUDE.md's release-workflow section.Why
An agent twice documented a distribution channel as an available install route before the artifact was live there — first
pip install veralangbefore it was on PyPI, then the VS Code Marketplace install route before the extension was accepted (backed out in #1107). The root cause is structural:AGENTS.mdhad no release-pathway or install-docs guidance at all, so the correction never stuck.Changes
AGENTS.md— new Releases and install docs section:release.yml→ approval-gatedpypienvironment → Trusted Publishing → tag + GitHub Release at the merge SHA); don't create tags, runtwine, orgh release create.README.md/SKILL.md/PYPI_README.md(source checkout = full environment and the recommended route for agents;pip install veralang= toolchain only; neverpip install vera), and never document a channel as available before it's live (the VS Code extension is still blocked — VS Code Marketplace rejects extension as suspicious content #1106).CLAUDE.md— the same unpublished-channel guard added to## Release workflow(its mechanics were already correct).docs/llms-full.txt— regenerated byscripts/build_site.py.Docs-only; no version bump.
check_doc_counts,check_site_assets, andcheck_changelog_updatedall pass locally.🤖 Generated with Claude Code