The release workflow is not needed when creating releases through
GitHub's UI. The workflow was failing because:
1. Creating a release in GitHub UI automatically creates the tag
2. The tag creation triggers the workflow
3. The workflow tries to create a release that already exists
Since releases are being created manually through the UI, this
workflow adds no value and only causes confusion with failures.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-authored-by: Claude <noreply@anthropic.com>
This file provides essential guidance for future Claude instances working
on this repository, including:
- Common development commands
- High-level architecture overview
- Testing structure and local testing instructions
- Build process details
- Key design decisions
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-authored-by: Claude <noreply@anthropic.com>
This prevents Dependabot PRs from failing CI due to package-lock.json
formatting differences. The file is auto-generated by npm and its exact
formatting is not important as long as it's valid JSON.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Runs lint-staged for automatic formatting of JS/JSON/YAML
- Runs pre-commit for all validation checks
- Ensures code quality before commits reach the repository
- Prevents CI failures due to formatting issues
- Enable automatic dependency updates for npm packages
- Enable automatic updates for GitHub Actions
- Group updates to reduce PR noise:
- Production dependencies in one group
- Development dependencies in another group
- All GitHub Actions updates grouped together
- Schedule weekly checks on Mondays
- Replace individual lint/test/build steps with pre-commit action
- Ensures CI runs exactly the same checks as local development
- Includes dist up-to-date check via pre-commit hooks
- Remove all Go code and replace with Node.js GitHub Action
- Use official golang.org/x/exp/cmd/apidiff tool
- Add PR comment functionality
- Support both git refs and directory comparisons
- Add comprehensive test suite with testdata examples
- Update CI to test action with breaking/safe/clean examples
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
golangci-lint v2.3.0 works best with default configuration
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add pre-commit configuration for code quality checks
- Set up GitHub Actions for CI with test, lint, and build jobs
- Add golangci-lint configuration
- Create Makefile for common development tasks
- Update README with development instructions
- Fix code formatting issues
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
A Go tool that analyzes API changes between two versions and reports breaking changes.
Features:
- Detects breaking API changes in Go code
- Compares git refs or directories
- Ignores internal/ packages by default
- Multiple output formats: text, JSON, markdown
- CI-friendly exit codes
Built on top of golang.org/x/exp/apidiff which provides the core API analysis.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
