[Tracking] GitVersion v7 release roadmap

[arturcic]

Purpose

Track and order the remaining GitVersion v7 work across the 7.0.x and 7.1.x delivery milestones. The 7.x umbrella milestone contains this roadmap, #2275 (New CLI), and #5031 (managed Git). Existing umbrella issues retain their own sub-issues; this roadmap links only their top-level parents plus standalone work. Umbrella milestone membership does not make all remaining umbrella work a v7.0 release gate; delivery scope is tracked by the release milestones and completion groups below.

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.
  • Package-build CI now exercises managed Git through merged #5175.
  • v7.0 defaults to managed Git, with GITVERSION_GIT_BACKEND=libgit2 retained as the temporary fallback; completed by merged #5189.
  • #5040 removes LibGit2Sharp in v7.1.
  • #5041 is an optional v7.1 accelerator, blocked by v7.1: remove LibGit2Sharp and native binaries #5040, and is not a release gate.
• #5131 — calculation/output configuration umbrella
  • #5132 — Versioned configuration, merged in #5158.
  • #5133 — Migration and legacy warnings, merged in #5159.
  • #5134 — Schemas and migration guidance, merged in #5160.
  • Configuration foundation complete. #5135 owns v7.0 defaults/selectors; #5188 owns v7.1 legacy parser/configuration runtime removal, outside the v7.0 release gate.
• #5130 — Regex-based branch and tag exclusions
  • Completed by #5147 — support regex tag exclusions and #5148 — support regex branch exclusions.
• #5135 — v7.0 defaults and feature selectors
  • Managed Git is the v7.0 default, with the temporary libgit2 fallback retained.
  • The configuration foundation [Feature] Group configuration under calculation and output sections with migration support #5131 is closed as completed; its dependency link records the satisfied prerequisite.
  • Align parser, configuration, and Git-backend defaults and selector behavior for v7.0.
  • Complete effective-selection logging and the documentation sweep.
  • Completed by #5189 — Default to v7 feature selections and standardize compatibility selectors, merged on 2026-09-08.
  • v7.1 legacy parser/configuration runtime removal is tracked separately by v7.1: remove legacy argument parser and v6 configuration runtime #5188.
  • Followed by the v8 cleanup in #5136.

The configuration foundation and v7.0 selector/default alignment are complete. Remaining v7.0 delivery work is tracked in Groups 2–4; legacy implementation removal remains in the v7.1 completion group below.

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
• #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
  • Resolved by merged #4977, whose tokenizer supports custom numeric formats such as 0000;;''. Closure verification on current main confirmed correct zero/nonzero results through both YAML configuration and CLI overrides; no further implementation is required.
• #3149 — Develop version after creating a release branch
  • Completed by #5192 — Track prerelease tags on unversioned release branches, merged on 2026-09-09. Develop can advance from eligible prerelease tags on release branches without a version in their names; versioned release names retain precedence.
• #4433 — Prevent increment of merged branch in GitHub workflow
  • Implementation PR #5140 remains open.
• #4144 — =semver: none|minor|major|patch bump messages
• #4057 — Multiple mainline branches
• #3954 — Consistent GIT_BRANCH handling
• #3035 — {Sha} and {ShortSha} in branch labels
  • Completed by #5191 — Support commit SHA placeholders in branch labels, merged on 2026-09-09. Labels can use the commit being versioned, including historical calculations; named regex captures retain precedence. Documentation and generated schema are updated.

Group 4 — User experience and documentation

• #5187 — Improve documentation navigation and version clarity
  • Completed by merged #5185: clearer navigation, version-specific guides and API references, and a consistent accessible documentation experience. Also closes #4537 — Confusing documentation version links.
• #3915 — Document TrunkBased flow

Nested-configuration documentation is complete under #5134; the broader site experience is tracked separately in #5187. The init wizard (#3900) is scheduled for v7.1 and is outside the v7.0 release gate.

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.0 completion group

Tracked in the 7.0.x milestone, including #5135:

• #5131 — Configuration implementation, migration tooling, schemas, and guidance: Implement versioned calculation and output configuration #5132–Publish v7 configuration schemas and migration guidance #5134 are complete. Later legacy-runtime removal remains in the v7.1 group.
• #5031 / #5135 — Make managed Git the v7.0 default, retaining GITVERSION_GIT_BACKEND=libgit2 as the temporary fallback.
• #5135 — Complete v7.0 parser/configuration selector alignment: default to the v7 parser and nested configuration, preserve the temporary v6 fallbacks, validate selector values, and reject the retired boolean parser variable with replacement guidance.
• #5135 — Complete effective-selection logging and migration documentation without contaminating machine-readable output.
• #5187 — Improve documentation navigation and version clarity, completed by docs: redesign site with shared versioned guides and API references #5185.
• Release/CI foundations: #5090 — Docker Hub OIDC and #5103 — Self-repository Actions syntax.
• #3149 — Track prerelease tags on unversioned release branches, completed by #5192.
• #3035 — Support commit SHA placeholders in branch labels, completed by #5191.
• Resolve the remaining 7.0.x work in Groups 2–4: complete each item, move it to a later milestone, or explicitly record it as optional/deferred before the v7.0 release-readiness decision.

LibGit2Sharp and legacy parser/configuration removal belong to v7.1; selector removal belongs to v8. The optional #5041 accelerator is not a v7.0 release gate.

v7.1 completion group

Tracked in the 7.1.x milestone:

• #5040 — Remove LibGit2Sharp and native binaries
• #2921 — Remote-reference operation without local branch copies: scheduled for v7.1, when managed Git is the sole backend following v7.1: remove LibGit2Sharp and native binaries #5040; outside the v7.0 release gate.
• #5188 — Remove the legacy parser/configuration implementations and retain v7 compatibility diagnostics
• #3900 — Revamp the init wizard: scheduled for v7.1.
• #3981 — Trimming and AOT support
• #2138 — Core API without shell-out interoperability

Explicitly non-blocking follow-up

• #5041 — Commit-graph acceleration is scheduled in the 7.1.x milestone and blocked by v7.1: remove LibGit2Sharp and native binaries #5040 (LibGit2Sharp removal). It remains 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 roadmap and the [Feature] New CLI #2275 and [Feature] Replace LibGit2Sharp with a managed Git implementation (managed reads + git CLI writes) #5031 umbrellas on the 7.x milestone. Assign release-specific delivery issues to 7.0.x, 7.1.x, or the appropriate later 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.