Skip to content

🧊 Coldkeep v1.10.5 — Release Validation Debt Hardening

Choose a tag to compare

View all tags
@franchoy franchoy released this 21 May 05:27
· 649 commits to main since this release
v1.10.5
0ca921e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Coldkeep v1.10.5 — Release Validation Debt Hardening

Summary

Coldkeep v1.10.5 is a release-process and validation-debt hardening release in the v1.10 correctness train.

This release does not introduce user-facing product behavior changes. Its purpose is to make future Coldkeep releases safer, more auditable, and easier to validate by tightening the release workflow around checklist execution, local-vs-CI evidence, Codacy review, gosec baseline handling, release documentation consistency, tracker/matrix closure discipline, and final release-state hygiene.

What changed

Release process hardening

  • Added release final-state hygiene rules so PR, CI, Codacy, merge, tag, publication, branch removal, and clean-tree completion are tracked explicitly.
  • Standardized the Pre-PR Code Quality / Codacy-Risk Gate.
  • Added evidence rules for release-candidate documentation, PR notes, release notes, changelog updates, and final release closure.
  • Added a full local PRE_RELEASE_CHECKLIST.md execution report for v1.10.5.

Validation and evidence hardening

  • Recorded local validation and CI-simulation evidence.
  • Consolidated Phase 1–7 process policies into a validation regression matrix.
  • Added release-documentation consistency checks.
  • Added closure consistency checks for tracker/matrix decisions.
  • Recorded the release-candidate internal readiness review before full checklist execution.

Analyzer and Codacy workflow hardening

  • Captured and classified the v1.10.5 gosec baseline.
  • Defined the Codacy PR finding workflow.
  • Added rules for distinguishing baseline findings, release-delta findings, accepted findings, false positives, duplicates, and tooling/config noise.
  • Ran the Pre-PR Code Quality / Codacy-Risk Gate before PR creation.
  • Addressed the small Codacy review fixes that were made during PR review.
  • Confirmed no unclassified release-delta Codacy findings remained before merge.

Tracker and matrix closure discipline

  • Added a conservative closure report for v1.10.5.
  • Recorded 0 direct v1.10.5 product-behavior closures, because this release is process/validation hardening rather than a product-code fix release.
  • Documented inherited v1.10.4 closures separately.
  • Kept product-code, restore, recovery, GC, storage, and domain-specific rows open or triaged unless directly supported by v1.10.5 evidence.

Validation

The release branch completed the required local validation and PR validation sequence.

Local and Pre-PR validation included:

  • go vet ./...
  • go test ./internal/maintenance ./internal/retention -count=1
  • go test -race ./internal/maintenance ./internal/retention -count=1
  • targeted release-train test suite covering GC, Snapshot, Retention, Repair, Physical, Orphan, Report, DryRun, Destructive, Candidate, Parity, Concurrency, and Mutation paths
  • golangci-lint run ./...
  • staticcheck ./...
  • gosec ./...
  • git diff origin/main...HEAD -- '*.go'

Final validation outcome:

  • Local validation completed.
  • Full local PRE_RELEASE_CHECKLIST.md execution completed and documented.
  • Pre-PR Code Quality / Codacy-Risk Gate completed.
  • PR CI completed green.
  • Codacy review completed, with small fixes applied during PR review.
  • PR merged into main.
  • Feature branch removed.
  • v1.10.5 tag created.

Compatibility

No product behavior changes are intended.

This release does not change:

  • repository format,
  • storage format,
  • snapshot semantics,
  • restore behavior,
  • GC behavior,
  • CLI contract,
  • JSON contract,
  • database backend behavior,
  • CI workflow configuration,
  • dependency or toolchain versions.

Known notes

  • The gosec baseline was classified as part of the release process. Baseline findings remain tracked and should not be interpreted as newly introduced v1.10.5 release-delta issues.
  • Codacy remains a review and risk-surfacing tool, not an architectural authority.
  • Future releases should continue using the Pre-PR Code Quality / Codacy-Risk Gate before PR creation.
  • Final release-state hygiene should be kept current after merge, tag, GitHub release publication, and branch cleanup.
Assets 2
Loading
0 Join discussion