---
title: "Discussion on \"Build a Patch Ledger That Can Survive the Next Deployment\" | Hashnode"
description: "Discussion on \"Build a Patch Ledger That Can Survive the Next Deployment\". Track security patches by application, deployed artifact and evidence. Keep exceptions visible and recheck acceptance when deployments change."
url: "https://hashnode.com/posts/build-a-patch-ledger-that-can-survive-the-next-deployment/6ad946541877198bcb76c723"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Build a Patch Ledger That Can Survive the Next Deployment](https://stadiasoft.hashnode.dev/build-a-patch-ledger-that-can-survive-the-next-deployment?utm_source=hashnode&utm_medium=feed)

Track security patches by application, deployed artifact and evidence. Keep exceptions visible and recheck acceptance when deployments change.

Oct 21 · 7 min read · stadiasoft.hashnode.dev  
Read the article

-   [#php](https://hashnode.com/tag/php)
-   [#security](https://hashnode.com/tag/security)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[Faraz Ahmad](https://hashnode.com/@farazahmad759)

@farazahmad759

  
[View profile](https://hashnode.com/@farazahmad759)

Full Stack Developer

Full-stack developer at StadiaSoft, building practical APIs, SaaS products and developer tools. I write implementation-focused guides on Node.js, automation, email security and modern web technology.

## Responses 1

Markdown supported · ⌘↵ to post

[Damiano Bianda](https://hashnode.com/@damianobianda)

[Oct 26](https://hashnode.com/posts/build-a-patch-ledger-that-can-survive-the-next-deployment/6ad946541877198bcb76c723/comment/6adf27dd3dc566e46d074c42)

The ledger design ages well because it separates the artifact from the host - and the dotnet out-of-band release this weekend shows why that matters. A self-contained app or a container image carries its own runtime, so "host patched" and "application covered" stay different rows even after a successful update. The state that describes missing evidence ("we have not checked what this artifact bundles") is exactly what dotnet --list-runtimes can't give you for those deployments. Curious how you'd represent container rebuilds in the ledger: one row per image digest, or per application with the digest as evidence?
