Setup command now has three modes:
- Registry mode: interactive wizard to select packages
- Bootstrap mode: clones core-devops first, then wizard
- Repo setup mode: generates .core/{build,release,test}.yaml
Changes:
- setup: add interactive package selection with charmbracelet/huh
- setup: detect project type (go/php/node/wails) and generate configs
- setup: auto-detect GitHub repo from git remote
- ai: fix command examples (core dev -> core ai)
- ci: rename flag to --we-are-go-for-launch
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
core ci
Publish releases to GitHub, Docker, npm, Homebrew, and more.
Safety: Dry-run by default. Use --we-are-go-for-launch to actually publish.
Subcommands
| Command | Description |
|---|---|
| init | Initialize release config |
| changelog | Generate changelog |
| version | Show determined version |
Usage
core ci [flags]
Flags
| Flag | Description |
|---|---|
--we-are-go-for-launch |
Actually publish (default is dry-run) |
--version |
Override version |
--draft |
Create as draft release |
--prerelease |
Mark as prerelease |
Examples
# Preview what would be published (safe)
core ci
# Actually publish
core ci --we-are-go-for-launch
# Publish as draft
core ci --we-are-go-for-launch --draft
# Publish as prerelease
core ci --we-are-go-for-launch --prerelease
Workflow
Build and publish are separated to prevent accidents:
# Step 1: Build artifacts
core build
core build sdk
# Step 2: Preview (dry-run by default)
core ci
# Step 3: Publish (explicit flag required)
core ci --we-are-go-for-launch
Publishers
See example.md for publisher configuration.
| Type | Target |
|---|---|
github |
GitHub Releases |
docker |
Container registries |
linuxkit |
LinuxKit images |
npm |
npm registry |
homebrew |
Homebrew tap |
scoop |
Scoop bucket |
aur |
Arch User Repository |
chocolatey |
Chocolatey |
Changelog
Auto-generated from conventional commits. See example.md for configuration.