release
Cut an AgentOS release via the scripts/publish flow. Use when the user asks to release, publish, cut a release, or bump the AgentOS version.
소스 정보
- 저장소
- rivet-dev/agentos
- 최근 소스 활동
- 2026년 7월 28일 08:36
- 감지된 SKILL.md 언어
- 영어
- 스타
- 4,835
- 포크
- 270
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- release
- description
- Cut an AgentOS release via the scripts/publish flow. Use when the user asks to release, publish, cut a release, or bump the AgentOS version.
# AgentOS Release
The publish flow lives in `scripts/publish` and is driven by
`.github/workflows/publish.yaml`.
AgentOS is the source of truth. It publishes npm packages, crates, runtime
sidecars, Pyodide/R2 assets, and `@agentos-software/*` registry packages from
this repository. agentos releases are generated compatibility shims that
follow the AgentOS version; never release agentos first.
## Procedure
1. Start from a clean, pushed `merge-aos` or `main` bookmark.
2. Run the local trigger:
```bash
just release --version 0.2.0 # exact version
just release --version 0.2.0-rc.1 # rc (npm tag `rc`)
just release --patch # semver bump from latest git tag
```
3. Watch the workflow:
```bash
run=$(gh run list -R rivet-dev/agentos --workflow=publish.yaml -L1 --json databaseId --jq '.[0].databaseId')
gh run watch -R rivet-dev/agentos "$run" --exit-status
```
## Notes
- Never publish to npm or crates.io locally; always go through `publish.yaml`.
- `scripts/publish/src/local/cut-release.ts` is a pure trigger; version changes
happen in the ephemeral CI checkout.
- `workspace:*` deps are rewritten to literal versions by the publish bump pass.
- Generated agentos shims are dispatched after AgentOS publishes and must
use the same version.
- If anything fails, stop and report — do not retry automatically.
GitHub에서 보기