Skip to content

chore: release v0.2.0 - #3

Merged
solomonneas merged 4 commits into
mainfrom
chore/v0.2.0-release
May 16, 2026
Merged

chore: release v0.2.0#3
solomonneas merged 4 commits into
mainfrom
chore/v0.2.0-release

Conversation

@solomonneas

Copy link
Copy Markdown
Collaborator

Summary

Prepares v0.2.0 release: distribution, CI coverage, project meta files, and a couple of fixes earned along the way.

Distribution

  • Add .github/workflows/publish.yml - tag-triggered build + twine upload via PYPI_API_TOKEN (already set as a repo secret). Includes a tag/version sanity gate.
  • Bump pyproject.toml + __init__.py to 0.2.0.
  • Add CHANGELOG.md (Keep a Changelog).
  • README: PyPI install path, doctor sample output, idempotency note, no-telemetry section.

CI

  • install-from-source smoke now matrixes over all six profiles (was workspace-only).
  • Pin content-guard checkout to 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}.yml plus config.yml to disable blank issues and link the cookbook.

Fixes earned along the way

  • publisher profile now extends: repo so it inherits AGENTS.md + handoff inbox; doctor was failing on a fresh publisher install.
  • init --profile hermes prints a stderr NOTE in addition to the post-install line so the experimental status is harder to miss.

Test plan

  • pytest -q passes (50/50)
  • All six profiles green locally:
    repo (exit=0): summary: 14 checks, 0 failed, 0 manual
    workspace (exit=0): summary: 14 checks, 0 failed, 0 manual
    openclaw (exit=0): summary: 22 checks, 0 failed, 0 manual
    hermes (exit=0): summary: 18 checks, 0 failed, 1 manual
    generic (exit=0): summary: 14 checks, 0 failed, 0 manual
    publisher (exit=0): summary: 14 checks, 0 failed, 0 manual
    
  • content-guard pre-push hook clean (with inline allow tag on the policy-doc contact emails)
  • CI green on this PR
  • After merge: tag v0.2.0, watch publish.yml, verify pip install solo-mise==0.2.0 works

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
@coderabbitai

coderabbitai Bot commented May 16, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@solomonneas has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 46 minutes and 18 seconds before requesting another review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1059c3c5-1e86-4f6b-8fd5-319a896aae99

📥 Commits

Reviewing files that changed from the base of the PR and between 17e1616 and 88c6560.

📒 Files selected for processing (15)
  • .github/ISSUE_TEMPLATE/bug.yml
  • .github/ISSUE_TEMPLATE/config.yml
  • .github/ISSUE_TEMPLATE/ingester-misclassified.yml
  • .github/ISSUE_TEMPLATE/profile-init-fails.yml
  • .github/workflows/ci.yml
  • .github/workflows/publish.yml
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
  • CONTRIBUTING.md
  • README.md
  • SECURITY.md
  • pyproject.toml
  • src/solo_mise/__init__.py
  • src/solo_mise/init.py
  • src/solo_mise/templates/profiles/publisher.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/v0.2.0-release

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@solomonneas
solomonneas merged commit db6eb78 into main May 16, 2026
11 checks passed
@solomonneas
solomonneas deleted the chore/v0.2.0-release branch June 10, 2026 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant