chore: release v0.2.0 - #3
Conversation
publisher.json now extends repo so it inherits AGENTS.md, CLAUDE.md, the handoff inbox, and the pre-push hook. Doctor was failing on a fresh publisher install because the profile was a slim add-on but doctor expected the workspace baseline. init now prints a stderr NOTE when --profile hermes is selected, in addition to the existing post-install note, so the experimental status is harder to miss.
ci.yml install-from-source job now runs against repo, workspace, openclaw, hermes, generic, and publisher so template drift in any profile is caught. Each smoke target gets a git init first because the repo profile installs a pre-push hook. content-guard checkout pinned to v0.1.1 instead of the default branch, so upstream changes there cannot redden us. publish.yml builds an sdist + wheel on v* tags and pushes to PyPI via the PYPI_API_TOKEN secret. Includes a tag/version sanity gate so a mistyped tag cannot ship the wrong version.
CONTRIBUTING covers local dev, adding profiles, adding doctor checks, and graduation criteria for experimental adapters. SECURITY routes vuln reports to email, lists in/out of scope, and aims for a 14-day fix window. CODE_OF_CONDUCT references Contributor Covenant 2.1 by URL rather than inlining the full text. Issue templates cover bug, profile-init-fails, and ingester-misclassified, plus a config.yml that disables blank issues and redirects general questions to the cookbook.
- Bump pyproject.toml + __init__.py to 0.2.0 - Add CHANGELOG.md following Keep a Changelog - README: add doctor sample output, PyPI install path, idempotency note, and privacy / no-telemetry section
|
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 (15)
✨ 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 |
Summary
Prepares v0.2.0 release: distribution, CI coverage, project meta files, and a couple of fixes earned along the way.
Distribution
.github/workflows/publish.yml- tag-triggered build + twine upload viaPYPI_API_TOKEN(already set as a repo secret). Includes a tag/version sanity gate.pyproject.toml+__init__.pyto0.2.0.CHANGELOG.md(Keep a Changelog).CI
install-from-sourcesmoke now matrixes over all six profiles (was workspace-only).v0.1.1(was tracking default branch).Project meta
CONTRIBUTING.md- local dev, adding profiles, doctor checks, experimental-adapter graduation criteria.SECURITY.md- private email reports, in/out of scope, 14-day fix window.CODE_OF_CONDUCT.md- references Contributor Covenant 2.1 by URL..github/ISSUE_TEMPLATE/{bug,profile-init-fails,ingester-misclassified}.ymlplusconfig.ymlto disable blank issues and link the cookbook.Fixes earned along the way
publisherprofile nowextends: reposo it inherits AGENTS.md + handoff inbox; doctor was failing on a fresh publisher install.init --profile hermesprints a stderr NOTE in addition to the post-install line so the experimental status is harder to miss.Test plan
pytest -qpasses (50/50)v0.2.0, watchpublish.yml, verifypip install solo-mise==0.2.0works