This release includes 4 breaking changes for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
Summary
AI summaryRemoved attachment upload functionality for issues and releases.
Full changelog
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: https://github.com/raohwork/forgejo-mcp/compare/v0.0.3...v0.0.4
Breaking Changes
- Removed attachment upload functionality for both issues and releases.
- Removed `CreateIssueAttachmentImpl` tool.
- Removed `CreateReleaseAttachmentImpl` tool.
- Removed client attachment upload methods.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About raohwork/forgejo-mcp
An MCP server for managing your repositories on Forgejo/Gitea server.
Related context
Beta — feedback welcome: [email protected]