[Tracking] GitVersion v7 release roadmap

[arturcic]

Purpose

Track and order the remaining GitVersion v7 work across the 7.x and 7.1.x milestones. Existing umbrella issues retain their own sub-issues; this roadmap links only their top-level parents plus standalone work.

The order below is the recommended delivery order. Explicit GitHub blocking relationships remain authoritative where present. Items within the same group may proceed in parallel when they do not share dependencies.

Group 1 — Release foundations and compatibility

These establish the architecture, configuration contract, migration path, and feature-selector lifecycle needed by the rest of v7.

• #5031 — Managed Git implementation umbrella
  • Core managed implementation is complete: #5042 — Git CLI writes and network operations established the mutating backend, and #5084 — fully managed Git backend landed the managed reader and parity coverage on main.
  • #5040 removes LibGit2Sharp in v7.1.
  • #5041 is an optional accelerator and is not a release gate.
• #5131 — calculation/output configuration umbrella
  • Remaining implementation order: #5132 → #5133 → #5134.
  • Branch and tag exclusions from #5130 landed first and should be migrated into the nested configuration layout with the rest of the calculation settings.
• #5130 — Regex-based branch and tag exclusions
  • Completed by #5147 — support regex tag exclusions and #5148 — support regex branch exclusions.
• #5135 — Align v7 selectors and remove legacy implementations in v7.1
  • Blocked by #5131.
  • Coordinates the v7 parser, configuration, and Git-backend defaults.
  • Followed by the v8 cleanup in #5136.

Critical configuration path:

#5132 → #5133 → #5134 → close #5131 → #5135

Group 2 — Platform and breaking-change work

Review these after the release foundations are stable; implementation can be parallelized where independent.

• #2275 — New CLI umbrella
• #3041 — Separate SemVerSource from CommitCountSource
• #3981 — Trimming and AOT support
• #4998 — .NET 11 support

Group 3 — Version-calculation behavior and API capabilities

Prioritize confirmed regressions before new behavior, then complete independent feature work.

• #4654 — Incorrect assembly-informational-version output
• #3149 — Develop version after creating a release branch
• #4433 — Prevent increment of merged branch in GitHub workflow
• #4144 — =semver: none|minor|major|patch bump messages
• #4057 — Multiple mainline branches
• #3954 — Consistent GIT_BRANCH handling
• #3035 — {Sha} and {ShortSha} in tag configuration
• #2921 — Remote-reference operation without local branch copies
• #2138 — Core API without shell-out interoperability

Group 4 — User experience and documentation

• #3900 — Revamp the init wizard for v7
• #3915 — Document TrunkBased flow

Documentation tied directly to the nested configuration remains in #5134 and should not be duplicated here.

Group 5 — Release and CI infrastructure

• #5090 — Docker Hub OIDC publishing
• #5103 — Self-repository syntax for Actions and workflows

These can proceed independently but must be resolved or explicitly deferred before the v7 release-readiness decision.

v7.1 completion group

Tracked in the 7.1.x milestone:

• #5040 — Remove LibGit2Sharp and native binaries
• #5135 — Remove the legacy parser/configuration implementations and retain only v7 compatibility diagnostics

Explicitly non-blocking follow-up

• #5041 — Commit-graph acceleration is optional and must not block v7.
• #5136 — Remove feature-selector environment variables is the v8 follow-up in the 8.x milestone.

Release-management rules

• Keep this issue on the 7.x milestone.
• Add new v7 work to the appropriate group and as a direct sub-issue unless it belongs under an existing umbrella.
• Do not duplicate grandchildren such as #5132–#5134 or #5040–#5041 as direct sub-issues here.
• Move explicitly scheduled v7.1 work to the 7.1.x milestone while retaining its parent hierarchy.
• Before releasing v7.0, every open item must be completed, moved to a later milestone, or explicitly marked optional/deferred.