Repository navigation
Releases
Releases · GarthDB/act-testing-mcp
v1.1.2
Patch Changes
v1.1.1
Patch Changes
-
#5
2957e9cThanks @GarthDB! - Simplify MCP configuration to match community standards- Remove PROJECT_ROOT requirement from default configuration
- Follow Browser MCP pattern with simple npx setup
- Add PROJECT_ROOT as optional override for specific use cases
- Update example configuration to be path-agnostic
- Reference Browser MCP documentation for consistency
This makes the setup much simpler for most users while still providing flexibility when needed. The new default configuration works out of the box without requiring project-specific paths, following established MCP community patterns.
v1.1.0
Minor Changes
-
#3
bb768a0Thanks @GarthDB! - Add npm provenance support for enhanced supply-chain security- Add
--provenanceflag to changeset publish command - Configure
publishConfig.provenance: truein package.json - Add
id-token: writepermission to release workflow - Enables verifiable attestations for published packages
This implements npm provenance as described in https://docs.npmjs.com/generating-provenance-statements, providing:
- Verifiable link to package source code and build instructions
- Public transparency log via Sigstore
- Enhanced supply-chain security for package consumers
- Automatic attestation generation during CI/CD publishing
- Add
Patch Changes
-
#3
8587e72Thanks @GarthDB! - Improve configuration documentation and add GitHub PR template- Add npx as the recommended installation method to resolve IDE compatibility issues
- Provide three configuration options: npx (recommended), global, and local development
- Update example configuration to use npx by default
- Add comprehensive GitHub PR template with checklists and sections
- Reference continuedev/continue#4791 about NPX availability problems in IDEs
This makes the MCP server more reliable across different IDE environments and provides better guidance for contributors.
v1.0.0
Patch Changes
- #1
6fc2d87Thanks @GarthDB! - Add comprehensive development tooling setup- Add changeset support for automated version management and releases
- Add commitlint with conventional commit message validation
- Add prettier with automatic code formatting on commit
- Add husky for git hooks (pre-commit and commit-msg)
- Add GitHub Actions workflows for CI/CD and automated releases
- Set up lint-staged for pre-commit code formatting
- Configure proper release automation with changesets and GitHub Actions