developer-release

# Release and CLI Stability Use this reference for release management procedures, understanding what constitutes a breaking CLI change, firewall log parsing, and Go module summaries. ## Table of Contents - [Release Management](#release-management) - [Firewall Log Parsing](#firewall-log-parsing) - [Breaking CLI Rules](#breaking-cli-rules) - [Go Module Summaries](#go-module-summaries) ## Release Management The project uses a minimalistic changeset-based release system inspired by `@changesets/cli`. ### Commands #### version (Preview Only) The `version` command operates in preview mode and never modifies files: ```bash node scripts/changeset.js version # Or make version ``` This command: - Reads all changeset files from `.changeset/` directory - Determines the appropriate version bump (major > minor > patch) - Shows a preview of the CHANGELOG entry - Never modifies any files #### release [type] [--yes|-y] The `release` command creates an actual release: ```bash node scripts/changeset.js release # Or (recommended - runs tests first) make release ``` This command: - Checks prerequisites (clean tree, main branch) - Updates `CHANGELOG.md` with new version and changes - Deletes processed changeset files (if any exist) - Automatically commits the changes - Creates and pushes a git tag for the release **Flags:** - `--yes` or `-y`: Skip confirmation prompt ### Release Workflow ```mermaid graph TD A[Add changeset files] --> B[Preview with version command] B --> C...