changesets
Use when a PR changes any released package (crates/*, sdk/typescript, sdk/python, packages/edit-tools), when the changeset-gate CI check fails, when adding a new crate or package to the release config, or when working on knope versioning/release automation. For the step-by-step workflow to add a change file, use $create-changeset.
- License 许可
- MIT
- 所属仓库
- RoderAI/roder
- 最近更新
- 2026-11-13
- Stars
- ★ 9
- Forks
- 1
01 前言 Front Matter
- name
- changesets
- description
- Use when a PR changes any released package (crates/*, sdk/typescript, sdk/python, packages/edit-tools), when the changeset-gate CI check fails, when adding a new crate or package to the release config, or when working on knope versioning/release automation. For the step-by-step workflow to add a change file, use $create-changeset.
03 SKILL.md 正文
Changesets & per-package versioning (knope)
This repo versions every Cargo crate and SDK package independently using
knope with changesets. Commit messages never bump
versions; only .changeset/*.md files do. Full docs: docs/releases.md.
Adding a changeset for a PR: use $create-changeset — it walks through
detecting touched packages, writing the file, verifying locally, and committing.
Add a changeset (required by CI)
Any PR touching files under a released package's directory must add a change
file in .changeset/:
---
roder-core: minor
roder: patch
---
# Short summary used in changelogs and release notes
- One file per logical change; name it descriptively, e.g.
.changeset/add_mcp_streaming.md. - Package names = keys in
knope.toml(crate names; SDKs areroder-sdk-typescript,roder-sdk-python,roder-edit-tools). - Bump types:
major|minor|patch. With this knope configuration, pre-1.0 breaking changes requiremajor(for example, 0.2.x to 0.3.0);minorandpatchboth advance the final component. Include the compatible reverse dependency closure when shared Rust API types change. - Never put non-changeset
.mdfiles (READMEs etc.) in.changeset/. - Commit the changeset — CI only counts files in the branch diff.
Verify locally before pushing:
python3 scripts/check-changesets.py --base origin/master
Test-only or comment-only changes inside a package can bypass the gate with
the skip-changeset PR label instead of a changeset.
Adding a crate or package
-
New crates get an explicit
version = "0.1.0"inCargo.toml— the workspace has no shared version, do not useversion.workspace = true. -
Regenerate the release config (CI checks it's current):
python3 scripts/generate-knope-config.py -
Non-Rust packages: add to
EXTRA_PACKAGESinscripts/generate-knope-config.pyfirst. -
knope.tomlis generated — never edit it by hand.
How releases happen (context)
- Push to
master→prepare-release.ymlrunsknope prepare-release, which consumes pending changesets, bumps affected packages, updates theirCHANGELOG.mds, and maintains theknope/releasepreview PR. - Merging that PR →
release.ymlrunsknope release, tagging<package>/v<version>and creating one GitHub release per package. - CLI npm publication and binary/Homebrew distribution run in release CI.
Crates.io and SDK registry publication are separate explicit steps; see
docs/releases.md. - Baseline tags for unreleased packages:
python3 scripts/init-release-tags.pyor the "Baseline release tags" workflow.
04 同仓库更多 Skills
repo-tour
Use when a user asks for an orientation tour of an unfamiliar repository. Produces a structured tour of entry points, key modules, and how to run tests.
review
Review code changes.
vcs-snapshot
Create a scoped version-control snapshot.
webwright
Drive a local Playwright browser through a Roder-owned Webwright workspace with plan, final script, screenshots, logs, and verification evidence.
vcs-snapshot
Create scoped VCS snapshots from the current workspace state.
roder-config
Configure and live-reload Roder from pasted config snippets, especially MCP server JSON, without leaking secrets or enabling executable integrations without approval.