Make Forgejo discovery resilient and continuously refreshed #24
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#30 Establish a secure, persistent hosted deployment
Personal/backstage
#23 Verify the imported catalog end to end
Personal/backstage
Reference
Personal/backstage#24
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Goal
Replace startup-only discovery with an explicit refresh lifecycle. Evaluate a scheduled backend entity provider against the current generated-file script and document the selected architecture.
Acceptance criteria
Depends on
#23
Phase
2 — Useful developer workflows
Progress
PR #51 was merged to
mainasf4cbb1d; follow-up PR #52 was merged as1393edcon 2026-11-21. The scheduled provider imports only repository descriptors, parses them, canonicalizeskind:namespace/namerefs, and rejects invalid identities or collisions before applying a full snapshot. A rejected refresh preserves the last successful catalog; names are never rewritten.The design and collision policy are documented in
docs/forgejo-discovery.mdanddocs/decisions/001-forgejo-catalog-source-of-truth.md.Validation
Woodpecker PR pipeline #140 passed all steps, including E2E. Local validation passed: frozen install, typecheck, lint, formatting, backend build, and 12 tests across the full unit suite. All acceptance criteria are complete.