Snider f831fd6846 docs: restructure with Build/Publish sections and dynamic nav

- Move PHP and Go framework docs from /packages/ to /build/
- Move CLI docs from /packages/go/cmd/ to /build/cli/
- Add /publish/ section with docs for all release publishers:
  GitHub, Docker, npm, Homebrew, Scoop, AUR, Chocolatey, LinuxKit
- Add sidebar navigation for /publish/ section
- Update nav with Build, Publish, Deploy dropdowns
- Remove changelog, contributing, guide, and security sections
- Make sidebar auto-discover from packages, build, publish, deploy dirs

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

2026-01-29 22:20:32 +00:00

1.2 KiB

Raw Blame History

Publish

Release your applications to package managers, container registries, and distribution platforms.

Publishers

Provider	Description
GitHub	GitHub Releases with assets
Docker	Container registries (Docker Hub, GHCR, ECR)
npm	npm registry for JavaScript packages
Homebrew	macOS/Linux package manager
Scoop	Windows package manager
AUR	Arch User Repository
Chocolatey	Windows package manager
LinuxKit	Bootable Linux images

Quick Start

# 1. Build your artifacts
core build

# 2. Preview release (dry-run)
core ci

# 3. Publish (requires explicit flag)
core ci --we-are-go-for-launch

Configuration

Publishers are configured in .core/release.yaml:

version: 1

project:
  name: myapp
  repository: org/myapp

publishers:
  - type: github

  - type: docker
    registry: ghcr.io
    image: org/myapp

Safety

All publish commands are dry-run by default. Use --we-are-go-for-launch to actually publish.

# Safe preview
core ci

# Actually publish
core ci --we-are-go-for-launch

1.2 KiB Raw Blame History