release: v1.0.1#32
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The rest of the tree (README, install.ts, sample-workflow README, welcome panel) moved to `python -m pip install` for the v1.0.1 batch; extension.ts's file header still pointed users at the bare `pip install` form. Trivially confusing for anyone reading the top of the file. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Stability batch on top of v1.0.0 — three rounds of edge-case hardening covered by 57 new tests (194 → 251). No new features; no behavior change for users on the golden path. Folds the accumulated [Unreleased] entries into ## [1.0.1] and drops the empty Unreleased header so the publish.yml awk extractor lifts the right block into the GitHub release notes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
26290b6 to
25d43e7
Compare
Summary
Stability batch on top of v1.0.0 — three rounds of edge-case hardening (251 tests, was 194 at v1.0.0) plus the supply-chain hardening from #27 (CycloneDX SBOM + signed SLSA provenance attached to each release, publish-side
npm auditgate). Folds the accumulated[Unreleased]entries into## [1.0.1]so the publish.yml awk extractor lifts the right block into the GitHub release notes.What ships
Editor / extension
python -m pip installswitch so the Windows ExecutionPolicy + official-installer-without-pip combo stops blocking first-run installclient.onDidChangeStateScan Workspaceagainst a dead LSP surfaces a real error instead of false-successserverArgs—client.start()raced against a 30s timeoutdisabledProviderssilences lowercasedockerfile/jenkinsfile— case-insensitive glob matchpython -m pip installto match every other surfaceSupply chain (from #27)
gh attestation verify <vsix> --owner greylag-cinpm audit --omit=dev --audit-level=highgate on the publish workflowCut sequence
After this PR merges to
main:Publish workflow waits at
productionenv gate; on approval, runs the new SBOM/provenance steps, publishes to VS Code Marketplace + Open VSX, and creates a GitHub release with the.vsix, the SBOM, and notes lifted from the## [1.0.1]section.Verification
main(now includes b88b22f from ci: add SBOM, signed provenance, and publish-side npm audit #27)awk '/^## \[/{n++} n==2{exit} n==1{print}' CHANGELOG.mddry-runs the release-notes extraction and produces the## [1.0.1]block with the new Security section🤖 Generated with Claude Code