[Tracking] GitVersion v7 release roadmap

Aperta
#5,137 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
csharp, git
Ambito
release

Direzione di ricerca

Inizia dalle issue principali collegate e dalle milestone 7.0.x e 7.1.x; questa issue è una roadmap più che un'attività di implementazione autonoma. Esamina i gruppi rimanenti e le relazioni di blocco, quindi conferma che ogni elemento sia completato, spostato a una milestone successiva oppure contrassegnato esplicitamente come opzionale o rinviato prima di decidere se il release è pronto.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

breaking change pinned

Purpose

Track and order the remaining GitVersion v7 work across the 7.0.0, 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.

Current status — 2026-11-18

Updated by Codex on behalf of Artur (@arturcic).

Live issue-distribution snapshot checked 2026-11-18 07:45 CET: 16 open issues: 0 in 7.0.0 or 7.0.x, 11 in 7.1.x, 4 in 7.x (3 umbrella/tracking issues and #5267), and 1 in 8.x. No open issues are unmilestoned. Milestone totals below include both issues and PRs; this open-issue count excludes PRs.

  • Stable 7.0.0 is published from 8fd9e294be12083242079edf2bf4dae4c0956164, the same source revision as beta.2. GA release CI passed on attempt 2. The release milestone is closed; all 145 expected GitReleaseManager entries are included in the published notes.
  • .NET 11 GA adoption and compatibility work is complete under #5394. #5490's Intel macOS restoration is implemented by merged #5491, published in beta.2 and stable 7.0.0, and validated by actual beta.2 installation/execution on an Intel macOS Azure agent. The stable parent tool package maps osx-x64 to the public GitVersion.Tool.osx-x64 7.0.0 package; both macOS standalone archives were verified.
  • Open v7.x performance bug: #5267 — Slow branch-source discovery with many branches, area: Performance / Git history. Reproduction and profiling needed; no implementation PR or confirmed blocking dependency. This remains deferred outside the v7.0 completion gate.
  • Under team review: #4433 via PR #5140.
  • Scheduled for v7.1: #4057 and Mainline bug #5405 via open PR #5295. These fixes are not on main and must not be claimed as delivered in v7.0.
  • Draft implementation: #5040 via PR #5396, removing LibGit2Sharp and native Git payloads.
  • Draft implementation: #3981 via PR #5391, blocked by #5040. #2921 and optional #5041 also depend on #5040. These remain v7.1 work.
  • Distribution status rechecked: Homebrew 7.0.0 is merged and GitTools Actions v5.0.0 is public. winget #483008 and SchemaStore #6682 remain open for upstream review; submission is complete, upstream availability is pending.
  • Completed delivery recorded below includes #5245/#5246, #4998/#5207, #5210/#5393, #5263/#5264 and #5253/#5259.

v7.0 release verification — updated 2026-11-18

The approved stable 7.0.0 release is published from 8fd9e294be12083242079edf2bf4dae4c0956164. Core publication and stable docs verification are complete. Homebrew 7.0.0 is merged and stable GitTools Actions v5.0.0 is published. The winget 7.0.0 manifest and SchemaStore 7.0 schema PRs have been submitted; both upstream merges remain pending. Coverage, Sonar and security observations below retain the evidence from the 2026-11-17 source-readiness audit; they do not claim a new analysis of later main commits.

Area Verified state
Source and release CI Release-source workflows passed, including source CI and GA release CI, attempt 2: 85 successful jobs and two skipped jobs. Skipped jobs are not counted as passes. Stable docs were published separately after #5495 merged.
Coverage Codecov project and patch statuses pass; project coverage is 85.10%. The earlier pending/failing snapshot is superseded.
SonarCloud Main analysis records this exact revision and has an OK quality gate and zero unreviewed security hotspots. Seven previously documented maintainability findings remain: two static-local-function suggestions, four static-method suggestions, and one CSS-transition-properties suggestion. They remain separate existing backlog under the evidence recorded in #5394; this does not claim zero Sonar issues.
Security alerts No open GitHub Dependabot or Code Scanning alerts at the readiness check.
Release milestone The exact 7.0.0 milestone is closed with 0 open and 165 closed items (55 issues and 110 merged PRs). Its listing and milestone index agree. Every item has exactly one classification: 9 breaking changes, 27 features, 19 bugs, 14 improvements, 62 dependencies and 14 documentation entries (145 included); 20 build entries are intentionally excluded. No unmerged PRs, not-planned issues or duplicate PR/closing-issue pairs remain in the milestone.
Published 7.0.0 GA artifacts All 11 exact-version NuGet packages are public, including all eight runtime tool packages. All eight standalone archives have verified SHA-256 digests and architectures, including both macOS architectures. All 13 version-qualified Docker Hub manifests contain AMD64 and ARM64 images; stable latest matches GA. GHCR publication succeeded with recorded digests, although anonymous registry inspection returned HTTP 401. Chocolatey 7.0.0 is approved and its package tests are passing.
Intel macOS Actions #2287 merged after Azure build 13065 passed. Logs confirm .NET 11.0.100 osx-x64, installation of published beta.2 into darwin-x64, and successful tool execution. The macOS test job reports 221 passed and 25 skipped; skipped tests are not passes. Native-Intel beta.2 installation/execution remains the platform validation evidence. Stable 7.0.0 Intel package publication and the parent-package mapping have now also been verified; the stable-publication item in #5490 is checked.

GA approval and coordination

  • Refresh GitReleaseManager milestone inputs: #5480 — AngleSharp 1.10.4 and #5481 — coverlet.MTP 10.1.1 are assigned to 7.0.0; superseded AngleSharp #5471 was removed. The 7.0.x umbrella is now empty.
  • Remove stale delivery entries: unmerged #2272 and #5063, abandoned fixture migration #5038, and superseded managed-default plan #5039. Actual v7.0 managed-default delivery remains represented by #5135. Only milestone membership changed; labels and closed states were retained.
  • Coordinate stable GitTools Actions v5 availability. Stable v5.0.0 was published on 2026-11-18 at 05:25:59 UTC and is public, with draft and prerelease flags both false. The earlier pending-release snapshot is superseded. The GitVersion GA notification completed as a no-op because the configured 7.0.x range already includes 7.0.0; Actions v5 publication is now independently verified.
  • Obtain explicit maintainer approval and publish final 7.0.0 using the existing release workflow. The stable release is public and the milestone is closed. GitReleaseManager-generated notes were repaired and reconciled to all 145 expected entries, with 20 build entries excluded; no missing or duplicate entries remain.

The earlier dependency-note consolidation intentionally omitted 131 intermediate/obsolete Dependabot entries; #5471 is now additionally superseded by #5480. Preserve this policy rather than re-adding intermediate entries through a generic missing-PR scan. Keep grouped PRs when they contain the latest change for any remaining component. The targeted #5480/#5481 refresh is complete. GitReleaseManager remains the source of generated GA notes; the published notes reconcile to 145 categorized entries and 20 build exclusions.

Post-publication verification and remaining distribution work

  • Homebrew: publisher run succeeded on 2026-11-18. Homebrew PR #326269 is merged, including depends_on "dotnet" and --output json. The earlier publishing-credential failure is superseded by this successful run; #5494 fixed the tap/formula lookup issue.
  • winget manifest submission: publisher run succeeded on 2026-11-18 and created winget PR #483008. The PR is open for upstream review; this confirms submission, not merged winget availability. The earlier invalid-token failure is superseded by this successful run.
  • winget upstream merge and availability: PR #483008 remains open, with manual installation review pending. Submission and a successful publisher run do not mark this merge complete.
  • Verify the GitTools Actions GA notification: run completed as a no-op because 7.0.x already includes 7.0.0. Stable Actions v5.0.0 publication is now separately verified above.
  • Publish and verify stable 7.0 docs, migration links, and both output and configuration schemas. Merged #5495 fixes runtime-package input discovery. Docs publication and Pages deployment passed. Public docs and schemas return HTTP 200; the manifest identifies stable 7.0.0, net11.0 and exact GA source 8fd9e294be12083242079edf2bf4dae4c0956164.
  • SchemaStore submission: merged #5019 connects the publisher to successful docs publication. The docs publication run passed on 2026-11-18, including the SchemaStore job, and created SchemaStore PR #6682 as gittools-bot from gittools-bot/schemastore. The PR adds schema 7.0, makes it the default and updates the wrapper reference while preserving older versions. The PR link is included in the 7.0.0 release notes.
  • SchemaStore upstream merge and catalog availability: PR #6682 remains open; PR creation does not mark upstream publication complete.
  • Verify exact-version GA artifacts: all 11 NuGet/tool/MSBuild packages, all eight standalone archives, final multi-architecture Docker manifests and stable latest, approved Chocolatey publication with passing package tests, all 145 expected GitReleaseManager note entries, and the linked GA announcement. This records verification of newly published GA artifacts, separately from beta.2 validation.

Bot-fork synchronization was completed for the Homebrew and winget publishing forks using ancestry-checked non-force pushes. These active upstream repositories continue accepting commits; refresh their state at the GA cut. Fork drift alone and local OAuth scope limitations are not proof that CI publishing credentials will fail. The successful 6.8.0 Homebrew run remains the prior stable publishing reference.

Post-GA CI maintenance: #5496 — update GitTools cicd to v6 merged on 2026-11-18. This is subsequent main-branch maintenance, not a change to the published 7.0.0 source revision.

Group 1 — Release foundations and compatibility

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

The configuration foundation and v7.0 selector/default alignment are complete. Completed v7.0 delivery is recorded in Groups 2–5; remaining GA publication tasks are tracked in the readiness audit above. 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.

Group 3 — Version-calculation behavior and API capabilities

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

Group 4 — User experience and documentation

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

The optional CI follow-ups are resolved: #5220 is completed and #5221 is closed as not planned. Neither blocks v7.0.

v7.0 completion group

Completed delivery is recorded in the 7.0.0 release milestone, including #5135. The 7.0.x milestone remains available for subsequent patch work:

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:

Explicitly non-blocking follow-up

Release-management rules

  • Keep this roadmap and the #2275 and #5031 umbrellas on the 7.x milestone. Assign release-specific delivery issues to 7.0.0, 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.
Lingua principale
C#
Stelle
3.1k
Fork
661
Merge medio
7h 4m
PR unite (30g)
77

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di GitTools/GitVersion

Tutte le issue di GitTools/GitVersion

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.