AI repo versioning and changelogs via release-please — never edit CHANGELOG.md or pyproject version by hand. Use when the user asks about releases, version bumps, changelogs, or preparing a release.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Versions and changelogs in this repo are fully automated. Do not manually edit release artifacts in feature PRs.
CHANGELOG.mdversion = "..." in each package pyproject.toml.release-please-manifest.jsonConfig: release-please-config.json and manifest at repo root. Full lifecycle: docs/contributing/release-process.md.
.github/scripts/check-no-manual-release.sh fails PRs that modify:
CHANGELOG.md.release-please-manifest.jsonversion = "..." line in any pyproject.tomlException: release-please's own standing Release PR (opened by the Release Workflow App).
git-conventional-commits skill).feat(sdk): ..., feat(toolkit): ...).chore: stable release main per group-pull-request-title-pattern in release-please-config.json; target CalVer is in the PR diff, not the title).| Intent | Commit type | Notes |
|---|---|---|
| New feature | feat(scope): ... | Appears under release notes |
| Bug fix | fix(scope): ... | Bug Fixes section |
| Breaking change | feat(scope)!: ... + BREAKING CHANGE: footer | Major bump per package |
| Internal deps only | chore(deps): ... | Hidden from user-facing changelog |
CalVer scheme: YYYY.WW.PATCH — see docs/contributing/release-process.md.
Do not edit CHANGELOG.md or pyproject.toml version. Instead:
docs/contributing/release-process.md for hotfixes/RC/dev cuts.release/*Backport fixes from main with cherry-pick, not direct edits on the release branch.
| Rule | Why |
|---|---|
Cherry-pick from main | CI checks patch equivalence (git cherry vs main), not identical SHAs |
| Rebase and merge only | Squash collapses N commits → 1; release-please loses per-commit changelog entries |
| Conventional commit subjects | release-please attributes each merged commit to changelog sections |
| Skip release-please bot PRs | chore: hotfix release/... PRs are automation — CI skips lineage for release-please--* branches |
Script: .github/scripts/check-release-lineage.sh (runs in CI for human PRs targeting release/*; patch-equivalence only, no commit-metadata allowlist).
Bumping a published unique_toolkit / unique_sdk version inside the monorepo (e.g. assistants-core pyproject.toml) is a separate step after a stable AI release — not a manual ai-repo changelog edit. See model-deployment LESSONS-LEARNED for cherry-pick checklists.
hotfix-backport — cherry-pick workflow and rebase-merge rules for release/*git-conventional-commits — commit/PR title formatsecurity-maintenance — same no-manual-release rules for CVE/CodeQL PRsNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Implement comprehensive error handling for Python code paths to keep services resilient and user-friendly. Use when failures are currently silent or exceptions leak through.
The English summary is being prepared. Showing the original description.
Tabular and numerical data analysis with descriptive statistics and insights. Use when the user provides data, tables, CSVs, or numbers and wants analysis.
The English summary is being prepared. Showing the original description.
Financial factsheet analysis with key metrics extraction and investment rationale
The English summary is being prepared. Showing the original description.
Diagnose and fix CI failures without leaving your editor.
The English summary is being prepared. Showing the original description.
Reproduce ai-repo PR checks locally with Poe and CI scripts, including per-package typecheck and coverage behavior. Use when validating changes before push or when user asks which local commands match CI.
The English summary is being prepared. Showing the original description.
Ask clarifying questions before implementing to ensure Python requirements are understood. Use when a task lacks detail, dependencies are unclear, or multiple interpretations are possible.
The English summary is being prepared. Showing the original description.