Skip to content

Coldkeep v1.13.15 — Final v1.x Security, Reproducibility, and Operational Closure

Latest
Latest

Choose a tag to compare

View all tags
@franchoy franchoy released this 28 Aug 21:17
· 3 commits to main since this release
Immutable release. Only release title and notes can be modified.
v1.13.15
6a2417e
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.13.15

Coldkeep v1.13.15 is the final planned v1.x release. It completes the supported v1 engine release baseline without adding v2 product work.

Security and supported build

  • Updates golang.org/x/sys to v0.44.0 and closes the reachable Windows native-string boundary issue.
  • Keeps the module language floor at Go 1.25.0 and certifies release-critical builds with Go 1.26.7 and GOTOOLCHAIN=local.
  • Runs govulncheck v1.7.0 as a blocking Linux and Windows gate.
  • Reproves CI, Required Gate, CodeQL with zero open alerts, Codacy, governance, and the frozen v1.13.14 release identity.

Correctness and operational closure

  • Preserves the frozen v1 Engine, Catalog, storage, schema, and compatibility contracts.
  • Corrects release lifecycle validation so tagging, publication, and post-publication closure remain distinct, truthful stages.
  • Preserves the reviewed v1.13.15 product tree while publication and final closure proceed through their separately authorized phases.

Source-only distribution and contributors

  • Distributes Coldkeep as source only; no prebuilt Coldkeep executable or binary asset is attached.
  • Certifies go install github.com/franchoy/coldkeep/cmd/coldkeep@v1.13.15 on Linux, macOS, and Windows using Go 1.26.7.
  • Keeps contributor and devcontainer contracts reproducible, including PostgreSQL-backed development with generated development-only credentials.

Publication of v1.13.15 does not by itself declare v1.x fully closed. Protected post-publication reconciliation and the read-only terminal audit remain required. Future v1 maintenance requires a separately planned and explicitly authorized critical correctness or security fix. V2 planning review may follow final v1.x closure; v2 implementation has not started and requires a separate plan.

Assets 3
Loading