Reconcile roadmap and migration documentation with current Forgejo state #62
Loading…
Reference in a new issue
No description provided.
Delete branch "mcp/docs-forgejo-reconciliation"
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?
Baseline
main:62ec15362ca613854c111bd660727675af3081cbDocuments changed
docs/roadmap.mddocs/latest-stable-upgrade-plan.mdversion-control.mddocs/dependency-compatibility-inventory.mddocs/README.mdREADME.mdAGENTS.mdNo application source, tests, Gradle/dependency pins, workflows, or runtime behavior are changed.
Reconciled state
Dependency migration
version-control.mdnow describes the live Forgejo CI surface: self-hostedlinux-amd64, the digest-pinned BookWave CI image, exact checkout/cache/upload action refs, Gitleaks 8.30.1, and the remainingactions/download-artifact@v3compatibility tag.Tracker inconsistencies intentionally not changed
Those tracker states are documented here but were not edited by this documentation-only PR.
Concurrent work kept separate
PR #61 owns the current #34/#35 implementation and edits ADR-0029 /
docs/risks.md. This PR intentionally does not pre-accept that work or modify those files.