mirror of
https://github.com/redwoodjs/local-ci.git
synced 2026-09-19 07:54:29 +08:00
Peter Pistorius
5b8acda506
- Rename package from 'machinen' to 'agent-ci' across all source, tests, scripts, configs, and docs - Rename CLI binary from 'machinen' to 'agent-ci' - Rename .machinen → .agent-ci, .env.machinen → .env.agent-ci, MACHINEN_* → AGENT_CI_* - Rename --runner flag to --name/-n (--runner still accepted for compat) - agent-ci-dev script now builds DTU before running CLI - Extract YAML compatibility tables to cli/compatibility.md - Expand CLI usage docs with per-command flag tables - Document DOCKER_HOST support for remote Docker
1.6 KiB
1.6 KiB
Releasing
Agent CI uses Changesets to manage versioning and publishing. The CLI (agent-ci) and DTU (dtu-github-actions) are always released together at the same version.
Making a Release
1. Add a Changeset
When you make a change worth releasing, run:
pnpm changeset
This opens an interactive prompt where you:
- Select the packages affected (both are bumped together regardless)
- Choose the bump type:
patch,minor, ormajor - Write a summary of the change
This creates a markdown file in .changeset/ — commit it with your PR.
2. Merge to main
When your PR is merged, the release workflow runs automatically and creates a "Version Packages" PR that:
- Bumps versions in both
package.jsonfiles - Updates
CHANGELOG.mdin each package - Consumes the changeset files
Multiple changesets accumulate into a single Version PR.
3. Publish
Merge the "Version Packages" PR. The release workflow runs again, this time:
- Builds both packages
- Publishes to npm
- Creates git tags
Setup
The GitHub repo needs an NPM_TOKEN secret with publish access.
Local Commands
| Command | Description |
|---|---|
pnpm changeset |
Add a new changeset |
pnpm version |
Apply pending changesets locally (for testing) |
pnpm release |
Build all packages and publish to npm |
pnpm -r build |
Build all packages without publishing |