Skip to content

release(versioning): stabile 5.2.0 aus rc6 ableiten#93

Merged
tomtastisch merged 3 commits intomainfrom
codex/release/stable-5-2-0-from-rc6
Feb 18, 2026
Merged

release(versioning): stabile 5.2.0 aus rc6 ableiten#93
tomtastisch merged 3 commits intomainfrom
codex/release/stable-5-2-0-from-rc6

Conversation

@tomtastisch
Copy link
Owner

Ziel & Scope

  • Ziel: Promotion von v5.2.0-rc.6 auf stabile Release-Version v5.2.0 gemaess docs/versioning/001_POLICY_VERSIONING.MD.
  • Scope: Release-/Retention-Pipeline, Versioning-Dokumentation und RC-Retention-Regeln.
  • Nicht im Scope: fachliche Code-Features in src/FileTypeDetection/*.

Umgesetzte Aufgaben (abhaken)

  • SemVer-Einstufung nach Policy verifiziert: MINOR von 5.1.4 auf 5.2.0.
  • Release-Retention-Logik angepasst: RC wird nach vorhandenem Stable-Tag nicht mehr behalten.
  • OIDC-Fallback fuer NuGet-Unlist in release-retention integriert (NuGet/login).
  • Versionshistorie DE auf stabilen Stand v5.2.0 aktualisiert.
  • Versionshistorie EN auf stabilen Stand v5.2.0 aktualisiert.
  • Changelog DE von [Unreleased] auf [5.2.0] promoted.
  • Changelog EN von [Unreleased] auf [5.2.0] promoted.
  • Lokale Gates fuer Build/Test/Docs/Versioning/Security ausgefuehrt.

Nachbesserungen aus Review (iterativ)

  • Retention-Regel fail-closed konkretisiert: kein RC-Keep bei vorhandenem Stable-Tag.
  • Workflow auf deterministic key-resolution erweitert (OIDC output || secret fallback).
  • Release-Doku auf aktuellen stabilen Zielzustand vereinheitlicht.

Security- und Merge-Gates

  • required checks muessen vollstaendig gruen sein.
  • alle Review-Threads werden vor Merge resolved.
  • security/code-scanning/tools: 0 offene Alerts (Merge-Gate).
  • keine Secret-Werte in Logs/Commits eingefuehrt.

Evidence (auditierbar)

  • Dateien:
    • .github/workflows/release-retention.yml
    • tools/ci/release/retention_apply.sh
    • docs/versioning/002_HISTORY_VERSIONS.MD
    • docs/versioning/102_HISTORY_VERSIONS.MD
    • docs/versioning/003_CHANGELOG_RELEASES.MD
    • docs/versioning/103_CHANGELOG_RELEASES.MD
  • Befehle lokal (Exit-Code 0):
    • python3 tools/check-doc-consistency.py
    • python3 tools/check-docs.py
    • bash tools/ci/bin/run.sh version-convergence
    • dotnet restore FileClassifier.sln -v minimal
    • dotnet restore --locked-mode FileClassifier.sln -v minimal
    • dotnet build FileClassifier.sln -c Release --no-restore -warnaserror -v minimal
    • dotnet test tests/FileTypeDetectionLib.Tests/FileTypeDetectionLib.Tests.csproj -c Release --no-build -v minimal
    • bash tools/ci/bin/run.sh versioning-svt
    • bash tools/ci/bin/run.sh security-nuget

DoD (mindestens 2 pro Punkt)

  • Retention-Regel:
    • RC-Keep nur ohne Stable-Tag (retention_apply.sh konditional).
    • Bei Stable-Tag werden RC-Versionen in die Cleanup-Menge ueberfuehrt.
  • NuGet-Unlist-Faehigkeit:
    • release-retention hat id-token: write.
    • NUGET_API_KEY wird aus OIDC-Output oder Secret aufgeloest.
  • Versioning-Doku-Konvergenz:
    • DE/EN-History referenziert stabil v5.2.0.
    • DE/EN-Changelog fuehrt 5.2.0 als releasefaehigen Eintrag.

Copilot AI review requested due to automatic review settings February 18, 2026 09:05
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 20eb3d444f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Promotes v5.2.0-rc.6 to the stable release v5.2.0 and updates the release retention automation plus DE/EN versioning documentation to reflect the new stable state.

Changes:

  • Adjusted retention logic to stop keeping RC tags once a stable tag exists, and updated the retention workflow to support OIDC-based NuGet key resolution with secret fallback.
  • Promoted changelog entries from [Unreleased] to [5.2.0] (DE/EN) and updated version history “current state” text to stable v5.2.0 (DE/EN).

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
tools/ci/release/retention_apply.sh Changes which tags are preserved during retention cleanup (stable vs RC).
.github/workflows/release-retention.yml Adds OIDC permissions + NuGet/login and switches NuGet API key resolution to OIDC output with secret fallback.
docs/versioning/103_CHANGELOG_RELEASES.MD Promotes the current changelog section to 5.2.0 and documents retention/workflow changes (EN).
docs/versioning/003_CHANGELOG_RELEASES.MD Promotes the current changelog section to 5.2.0 and documents retention/workflow changes (DE).
docs/versioning/102_HISTORY_VERSIONS.MD Updates “current state” to stable v5.2.0 (EN).
docs/versioning/002_HISTORY_VERSIONS.MD Updates “current state” to stable v5.2.0 (DE).

@tomtastisch tomtastisch merged commit c1a2430 into main Feb 18, 2026
26 checks passed
@tomtastisch tomtastisch deleted the codex/release/stable-5-2-0-from-rc6 branch February 18, 2026 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:pipeline area:versioning ci CI/workflow change impl:config versioning:patch Fix/Refactor/Docs/CI/Tooling; requires PATCH bump

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments