Apply completion contract to release completion #750

Closed
opened 2026-05-14 03:07:06 +00:00 by barrettruth · 0 comments
Owner

Parent tracker: #744

Scope: make release tag completion obey the same no-synchronous-backend-fetch completion contract using cache-only or stale-cache plus async warming semantics.

Constraints: backend-neutral across GitHub, GitLab, Forgejo; preserve release browse/delete execution behavior.

Verification: release completion budget tests and full local CI before PR.

Parent tracker: #744 Scope: make release tag completion obey the same no-synchronous-backend-fetch completion contract using cache-only or stale-cache plus async warming semantics. Constraints: backend-neutral across GitHub, GitLab, Forgejo; preserve release browse/delete execution behavior. Verification: release completion budget tests and full local CI before PR.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/forge.nvim#750
No description provided.