8000 Tags · gsong/ccmcp · GitHub
[go: up one dir, main page]

Skip to content

Tags

Tags

v1.4.1

Toggle v1.4.1's commit message
No Features or Breaking Changes exist in this set, so I dropped those…

… two headings. The chore and docs commits went under Improvements, and the duplicate "routine repo maintenance" collapsed to one line.

```markdown

- Bump transitive postcss and nanoid to patched versions
- Bump transitive vite and esbuild to patched versions

- Use an optional chain in ConfigPreview
- Read the bumped version from `pnpm version --json`
- Migrate the build from tsup to tsdown
- Upgrade pnpm to 12 and refresh dependencies
- Repin GitHub Actions to current releases
- Ignore local mise overrides
- Correct the @types/node override rationale
- Routine repository maintenance
```

v1.4.0

Toggle v1.4.0's commit message
- Read bumped version from package.json in release script

- Decouple cache and config file extensions
- Extract shared constants
- Install zizmor via prebuilt binary instead of cargo
- Migrate pnpm config to pnpm-workspace.yaml
- Group renovate dependency updates by type
- Upgrade Node to 22 LTS, pnpm to 11, and all dependencies
- Update tsup target to node20
- Use .node-version file for Node.js version management
- Update GitHub Actions to latest versions
- Require 7-day minimum release age for dependencies

v1.3.0

Toggle v1.3.0's commit message
- Add actionlint for GitHub Actions workflow linting

- Update minimum Node.js version to 20 and add Node.js 24 support

- Reorganize npm scripts for clarity
- Upgrade all dependencies
- Pin GitHub Actions to commit SHAs with actions-up
- Prioritize major updates over minor and patch in Renovate

v1.2.2

Toggle v1.2.2's commit message
Looking at these conventional commits, they're all maintenance tasks …

…(chore/docs) with no user-facing features or bug fixes. Here are the release notes:

- Update all dependencies to latest versions
- Migrate from Vitest 3.2.4 to Vitest 4.0.3
- Update specifications to reflect current implementation

v1.2.1

Toggle v1.2.1's commit message
fix: use npm publish instead of pnpm for OIDC support

v1.2.0

Toggle v1.2.0's commit message
- Resolve CLI flag collisions with Claude Code passthrough

- Document git worktree support, TUI shortcuts, and cleanup behaviors

v1.1.0

Toggle v1.1.0's commit message
- Add git worktree support for shared selections

- Isolate cache directories in parallel test execution
- Prefix unused cmd parameter with underscore in tests

v1.0.0

Toggle v1.0.0's commit message
- Add cleanup command to remove stale configurations

- Move temp file cleanup after GitHub release creation

- Reorganize npm scripts with public/private separation

v0.6.0

Toggle v0.6.0's commit message
- Display version number in TUI header

- Add GitHub release creation to release script

- Replace manual shell escaping with shell-quote library for safer command execution

- Apply minor code quality improvements
- Add TypeScript erasableSyntaxOnly and verbatimModuleSyntax flags
- Add dependency injection for better testability
- Centralize process.exit() handling for better testability
- Extract package version reading to shared utility
- Optimize bundle size with tsup

v0.5.0

Toggle v0.5.0's commit message
- Remember user's last MCP config selections per project

- Display config labels at full width by default
- Add reusable test helper infrastructure
- Add project specifications

- Handle missing config directory per specification
- Restore vi.resetModules() call in config selection UI tests
- Replace non-null assertions with proper type narrowing in tests

- Remove 24 biome-ignore suppressions by improving test helper types
- Migrate claude-launcher tests to Vitest with improved mocking
- Adopt test helpers across multiple test files
- Remove unused replaceProcess option from claude-launcher
- Expand test coverage for ConfigSelector, mcp-scanner, and Claude Code launch behavior
0