release(core): PR-108-Audit wiederherstellen und Version-SSOT auf 6.0.0 stabilisieren#116
release(core): PR-108-Audit wiederherstellen und Version-SSOT auf 6.0.0 stabilisieren#116tomtastisch wants to merge 17 commits intomainfrom
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
@copilot review |
|
@tomtastisch I've opened a new pull request, #117, to work on those changes. Once the pull request is ready, I'll request review from you. |
github-actions
bot
added
feature
|
Evidenz-Update: Wiederumsetzung gegen PR108 vollständig verifiziert.
Umsetzung/Nachweis im Repo: Commit |
There was a problem hiding this comment.
Pull request overview
This PR performs a deliberate version rollback from 6.0.1 to 6.0.0 to stabilize the repository's version Single Source of Truth (SSOT). Additionally, it restores audit documentation from PR-108 that was lost during a branch reset. The PR explicitly documents that version 6.0.1 work is deferred to a follow-up PR, focusing this release solely on establishing a stable, pipeline-compatible 6.0.0 baseline.
Changes:
- Rolled back all version references from 6.0.1 to 6.0.0 across property files and project files
- Restored comprehensive PR-108 review audit documentation with 53 tracked threads
- Reordered version history and changelog documents to position 6.0.0 as the active version with 6.0.1 documented as deferred/planned work
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| Directory.Build.props | Rolled back RepoVersion from 6.0.1 to 6.0.0 |
| src/FileTypeDetection/FileTypeDetectionLib.vbproj | Rolled back Version and PackageVersion from 6.0.1 to 6.0.0 |
| docs/versioning/002_HISTORY_VERSIONS.MD | Updated working state to 6.0.0 and reordered version table to show 6.0.0 before deferred 6.0.1 |
| docs/versioning/102_HISTORY_VERSIONS.MD | Updated working state to 6.0.0 and reordered version table to show 6.0.0 before deferred 6.0.1 (EN) |
| docs/versioning/003_CHANGELOG_RELEASES.MD | Reordered changelog to place 6.0.0 section first, with 6.0.1 documented as deferred patch |
| docs/versioning/103_CHANGELOG_RELEASES.MD | Reordered changelog to place 6.0.0 section first, with 6.0.1 documented as deferred patch (EN) |
| docs/governance/047_PR_108_REVIEW_AUDIT_DE.MD | Added comprehensive audit documentation for PR-108 with full thread tracking and resolution evidence |
|
CI-Reparatur (1 Commit / 1 Ursache):
|
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.
Comments suppressed due to low confidence (1)
docs/versioning/103_CHANGELOG_RELEASES.MD:12
- In the changelog, the internal hashing service is referenced as
EvidenceHashingIo, but the implementation/type name in the codebase isEvidenceHashingIO(uppercase IO). This mismatch makes the entry hard to grep/verify and looks like a typo; please align the identifier in the changelog to the actual type name.
- New internal hashing services (`EvidenceHashingCore`, `EvidenceHashingRoundTrip`, `EvidenceHashingIo`) for deterministic extraction without adding dependencies.
- Changed:
Ziel & Scope
Diese PR stellt die nach dem Revert/Branch-Neuaufsetzen verloren gegangene Audit-Evidenz wieder her und stabilisiert die aktive Versions-SSOT bewusst auf
6.0.0(pipeline-kompatibel), ohne neue Feature- oder API-Änderungen einzuführen.Umgesetzte Aufgaben (abhaken)
codex/release/...) vonmainerstellt.docs/governance/047_PR_108_REVIEW_AUDIT_DE.MD.70Dateien) ergänzt: keine fehlenden Dateien, keine verlorenen Refactor-Artefakte.6.0.0konvergiert:Directory.Build.props(RepoVersion)src/FileTypeDetection/FileTypeDetectionLib.vbproj(Version,PackageVersion)docs/versioning/002_HISTORY_VERSIONS.MD(Top-Eintrag)102_...,103_...).6.0.0aktiv,6.0.1als nachgelagerte Nachversionierung dokumentiert.6.0.1.nupkgaus SVT-Pfad ausgeschlossen, neues6.0.0.nupkgerzeugt).Nachbesserungen aus Review (iterativ)
53Threads,unresolved=0(GitHub GraphQL).047_PR_108_REVIEW_AUDIT_DE.MD).file_count=70,missing_count=0, Threadstatus53/53 resolved).6.0.0fixiert (Folge-PR für Nachversionierung bleibt möglich).6.0.1-Artefakt im lokalenartifacts/nugetwar Ursache.Security- und Merge-Gates
SECURITY.mdunverändert (Repo-Contract eingehalten).security/code-scanning/toolsbleibt Merge-Blocker und muss auf0 offene Alertsstehen.Evidence (auditierbar)
Verwendete Kernbefehle:
dotnet restore --locked-mode FileClassifier.sln -v minimaldotnet build FileClassifier.sln --no-restore -warnaserror -v minimaldotnet test FileClassifier.sln --no-build -v minimaldotnet test tests/FileTypeDetectionLib.Tests/FileTypeDetectionLib.Tests.csproj -c Release --no-restore --filter "Category=ApiContract" -v minimalbash tools/ci/check-versioning-svt.sh --repo-root . --naming-ssot tools/ci/policies/data/naming.json --versioning-ssot tools/ci/policies/data/versioning.json --out artifacts/refactor_evidence/versioning-svt-summary.jsonROOT_DIR=. OUT_DIR=artifacts/refactor_evidence/version-convergence REQUIRE_REMOTE=0 bash tools/versioning/verify-version-convergence.shbash tools/audit/verify-security-claims.shgh pr view 108 --json files,mergeCommit+ Dateiexistenz-/Diff-Abgleich gegen aktuellen Branch (4badf0f..HEAD)Artefakte:
artifacts/refactor_evidence/restore.logartifacts/refactor_evidence/build.logartifacts/refactor_evidence/test.logartifacts/refactor_evidence/api-contract.logartifacts/refactor_evidence/versioning-svt-direct.logartifacts/refactor_evidence/version-convergence-direct.logartifacts/refactor_evidence/security-claims.logartifacts/refactor_evidence/preflight-local.logartifacts/refactor_evidence/pack.logDoD (mindestens 2 pro Punkt)
docs/governance/047_PR_108_REVIEW_AUDIT_DE.MDvorhandenUMGESETZT/ASSUMPTION/OFFEN)RepoVersion == Version == PackageVersion == 6.0.0docs/versioning/002_HISTORY_VERSIONS.MDist6.0.0dotnet buildgründotnet testgrün inkl. ApiContract-Filtercheck-versioning-svt.shgrünverify-version-convergence.sh (REQUIRE_REMOTE=0)gründotnet format --verify-no-changesgrünAssumption / Folge-PR
ASSUMPTION: Eine Nachversionierung auf
6.0.1oder6.1.xwird in einem Folge-PR separat entschieden, um diese PR auf den pipeline-stabilen Konvergenzstand6.0.0zu begrenzen.Verifikation für Folge-PR: API-Surface-Diff + Contract-Tests + SemVer-Entscheidungsprotokoll.