Releases: raohwork/forgejo-mcp
Releases · raohwork/forgejo-mcp
Release list
Add missing tool and fix milestone bug
New Features
- feat: add create_pull_request tool
Bug Fixes
- fix: include milestone ID in markdown output
Full Changelog: v0.0.6...v0.0.7
Upgraded MCP SDK from v0.2.x to v0.4.0
This version does not change any feature, just upgrade the MCP SDK.
Full Changelog: v0.0.5...v0.0.6
Minor improvements
This release introduces new features and important updates to improve functionality and maintain compatibility.
New Features
- Enhanced Issue Listing: The
list_repo_issuestool now supports since and before time filters, allowing for more precise querying of issues based on their update times.
Improvements & Refinements
- MCP SDK Update: Updated the Model Context Protocol (MCP) SDK to its latest version from the main branch, which includes various fixes and improvements to tool handlers, ensuring better compatibility and performance.
Full Changelog: v0.0.4...v0.0.5
Attachment Refactor and Project Enhancements
v0.0.4 - Attachment Refactor and Project Enhancements
What's Changed
🔧 Refactoring
- Removed attachment upload functionality: Streamlined the codebase by removing attachment upload tools and methods for both issues and releases
- Removed
CreateIssueAttachmentImpltool - Removed
CreateReleaseAttachmentImpltool - Removed client attachment upload methods
- Updated documentation to reflect changes
- Removed
💄 UI/UX Improvements
- Enhanced issue comment display format: Improved the response and display format for issue comments
🎨 Visual Identity
- Added AI-generated logo: Added a new project logo (
logo.svg)
🔧 Developer Experience
- Added glama.ai auto-discovery: Added spec file (
glama.json) for automatic discovery by glama.ai MCP registry - Environment updates: Various environment configuration improvements
📚 Documentation
- Updated documentation: Removed references to attachment upload functionality to align with code changes
Technical Details
This release focuses on code cleanup and project infrastructure improvements. The main change is the removal of attachment upload functionality, which simplifies the codebase while maintaining core MCP server functionality for Forgejo/Gitea integration.
Full Changelog: v0.0.3...v0.0.4
Issue Blocking, Transport Modes, and CI Improvements
🚀 New Features
- Issue Blocking: Introduced full support for issue blocking, allowing one issue to block another. (#1)
- Transport Modes: Implemented MCP (Machine-readable Command Protocol) over SSE (Server-Sent Events) and HTTP, providing more flexible communication
options. - Automatic Versioning: Version information is now automatically updated and injected during the CI release process.
✨ Improvements & Refactoring
- Optimized Output Formatting: Refactored several tools (Issue Dependencies, Milestones, Wiki, Issue Lists) to simplify output, making it more concise,
readable, and reducing token usage. - Code Structure: Relocated multiple data structures from the tools package to the types package for a cleaner project structure.
- Dependency Management: Simplified the success messages for adding/removing dependencies.
📦 CI/CD
- macOS Support: The CI pipeline now includes support for macOS environments.
- Docker Image Builds: Added a workflow for building Docker images.
📝 Documentation
- README: Improved the structure and clarity of the README file.
- Concept Clarification: Clarified the distinction between "dependencies" and "blocking" in the documentation.
- Package Documentation: Added package-level documentation for all subpackages.
Full Changelog: v0.0.2...v0.0.3
Initial release
Add Forgejo Actions release workflow Add automated release workflow that triggers on version tags: - Build cross-platform binaries (Linux/Windows, amd64/arm64) - Generate SHA1 checksums for all binaries - Create GitHub release with all artifacts - Run tests before building This enables automated releases when version tags are pushed. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>