Releases: bjoaquinc/mcp-error-formatter
Releases · bjoaquinc/mcp-error-formatter
v1.1.4: Fix CI/CD build order for tests
Fixed
- CI/CD workflow test failures due to incorrect build order
- Tests now run after TypeScript compilation, not before
- Fixed
prepublishOnlyscript order to build before testing - Resolved "Cannot find module '../dist'" errors in test suite
Changed
- GitHub Actions workflow now runs: build → lint → test (was: lint → test → build)
- Package.json
prepublishOnlyscript now runs: build → test (was: test → build)
This patch release fixes the test execution order so that TypeScript compilation happens before running tests, resolving the module import errors that were preventing successful CI/CD runs.
v1.1.3: Fix GitHub Packages publishing configuration
Fixed
- GitHub Packages publishing configuration and authentication
- Enhanced workflow with explicit registry configuration for dual publishing
- Added proper scope mapping for GitHub Packages registry
- Added
publishConfigwith public access for both registries
Changed
- Improved CI/CD workflow with explicit npm registry configuration
- Enhanced GitHub Packages publishing job with proper scope setup
- Added registry-specific configuration steps to prevent publishing conflicts
This patch release fixes the GitHub Packages publishing issues by adding proper registry configuration, scope mapping, and authentication handling. The package should now successfully publish to both npm and GitHub Packages registries.
v1.1.2: Add GitHub Packages publishing support
Added
- GitHub Packages publishing support in CI/CD workflow
- Dual registry publishing: packages now published to both npm and GitHub Packages
- Enhanced GitHub Actions workflow with parallel publishing jobs
Changed
- Updated GitHub Actions workflow to publish to both npm registry and GitHub Packages registry
- Added proper permissions for GitHub Packages publishing
Technical Details
- Added
publish-githubjob to workflow for GitHub Packages registry - Configured
npm.pkg.github.comregistry URL for GitHub publishing - Uses
GITHUB_TOKENfor GitHub Packages authentication - Maintains backward compatibility with existing npm publishing
This release enables dual publishing to both the public npm registry and GitHub Packages, providing users with more installation options and enterprise-friendly publishing.
v1.1.1: Add npm repository metadata
Added
- Repository, bugs, and homepage links to package.json for better npm page integration
- GitHub repository now visible on npm package page
This release improves the npm package page by adding proper repository metadata, making it easier for users to find the source code and report issues.