You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix: Add required jsonrpc field to JSON-RPC 2.0 responses
- Add 'jsonrpc': '2.0' field to all response messages
- Add 'jsonrpc' and 'id' fields to error responses
- Ensures full compliance with JSON-RPC 2.0 specification
* Docs/journey v1.4.0 update (#4)
* docs: Update JOURNEY.md with v1.4.0 release experience
- Added Phase 6 documenting v1.4.0 major release
- Documented critical logging fix and GG-SS reorganization
- Updated mcp-publisher path (cli/mcp-publisher → cmd/publisher)
- Added v1.4.0 timeline and publication process
- Updated Final Status section to reflect v1.4.0
- Added key learnings from registry structure changes
- Documented new features: 2 new tools, enhanced metadata
* feat: Update description and add project-level MCP config
- Update server.json description to match README positioning
- Add .mcp.json for project to use its own MCP server (dog-fooding)
- Update uv.lock to reflect v1.4.0
---------
Co-authored-by: Uttam Jaiswal <uttam.jaiswal@skill-mine.com>
---------
Co-authored-by: Uttam Jaiswal <uttam.jaiswal@skill-mine.com>
- ✅ Added 2 new MCP tools (get_practice_summary, search_practices)
913
+
- ✅ Enhanced list_practices with metadata
914
+
- ✅ Updated comprehensive CHANGELOG.md
915
+
- ✅ Merged PR #2 to main (12 commits, preserved history)
916
+
- ✅ Tagged v1.4.0 in git
917
+
- ✅ Built and published to PyPI
918
+
- ✅ Discovered registry path changed (cli → cmd)
919
+
- ✅ Published to MCP Registry with correct path
920
+
- ✅ Updated JOURNEY.md with v1.4.0 experience
921
+
728
922
---
729
923
730
924
## Resources and References
@@ -771,12 +965,15 @@ For anyone attempting a similar journey:
771
965
772
966
The DevOps Practices MCP Server is now live and available for the Claude AI community to use. It provides 11 best practices and 7 templates for infrastructure teams, all validated and published through proper channels.
0 commit comments