core/cli

Snider eed8a030f1 docs: add example.md files and ci subcommands

- Add example.md alongside index.md for config/usage samples
- Add ci subcommands: init, changelog, version
- Fix ci/index.md to reference correct commands (was release)
- Update references from config.md to example.md

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-29 14:54:44 +00:00

1.6 KiB

Raw Blame History

core ci

Publish releases to GitHub, Docker, npm, Homebrew, and more.

Safety: Dry-run by default. Use --were-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
`--were-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 --were-go-for-launch

# Publish as draft
core ci --were-go-for-launch --draft

# Publish as prerelease
core ci --were-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 --were-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.

1.6 KiB Raw Blame History