docs: propose releases support (closes #127) #129
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!129
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/129/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
OpenSpec proposal for adding Forgejo releases support to
forgejo-mcp, per issue #127.Adds a new openspec change
add-releases-support(proposal artifact only — design/specs/tasks follow in subsequent commits).Capability
New:
release-management— 13 MCP tools across two sub-surfaces:list_releases,get_release_by_id,get_release_by_tag,get_latest_release,create_release,edit_release,delete_release,delete_release_by_taglist_release_attachments,get_release_attachment,create_release_attachment,edit_release_attachment,delete_release_attachmentAll list endpoints satisfy
docs/design/output-bounding.md(client-controlledpage+limit).Dependencies
None new —
codeberg.org/mvdkleijn/forgejo-sdk/forgejo/v3 v3.0.0already exposes every required method.Status
This PR is proposal-only. Implementation lands in a follow-up once the proposal is acknowledged.
Test plan
openspec validate add-releases-supportpasses once specs + tasks land