deps: migrate forgejo-sdk from v2 to v3 #100
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!100
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/100/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
codeberg.org/mvdkleijn/forgejo-sdk/forgejo/v2tov3Details
forgejo-sdk v3.0.0 is now available. The v2→v3 migration is a clean import path swap across 21
.gofiles plusgo.mod/go.sumupdates. No code logic changes required.This unblocks future work that depends on v3-only SDK features (e.g. quota APIs, context-aware methods).
Test plan
go build ./...passesgo test ./...passes (all 5 test suites green)