Merged
Conversation
Introduce schema v1.2.1 which adds dual entry-point configuration (mcp_server + hatch_mcp_server) and enforces that all declared tools exist on the FastMCP server implementation.
feat(schemas): add package schema v1.2.1 with dual entry-point support
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces Hatch Package Schema version 1.2.1, which adds dual entry point support for packages and strengthens tool validation requirements. The documentation has been updated to reflect these changes, including migration guidance, new examples, and an updated JSON schema. These improvements enhance separation of concerns, external compatibility, and package validation across the ecosystem.
Schema and Validation Enhancements
package/v1.2.1/hatch_pkg_metadata_schema.jsonwith support for dual entry points (mcp_serverandhatch_mcp_server) and enforced tool declaration requirements.Documentation Updates
README.mdanddocs/package/overview.md, including versioned schema lists and example metadata. [1] [2]Migration Support
docs/package/v1.2.1_migration_guide.md) detailing the steps and requirements for upgrading packages from v1.2.0 to v1.2.1, including code samples and troubleshooting tips.