From 571944106d0593eb9022ec579199766313f37f24 Mon Sep 17 00:00:00 2001
From: Miguel Martinez Trivino <miguel@chainloop.dev>
Date: Fri, 16 Oct 2026 15:16:04 +0200
Subject: [PATCH] docs: add last updated timestamp to README

Assisted-by: Claude Code
Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>

Chainloop-Trace-Sessions: 86ebe0d0-f32b-4c97-af5b-2ea38d3225fe
---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index 745248368..276c4ac90 100644
--- a/README.md
+++ b/README.md
@@ -25,6 +25,8 @@
   <a href="https://github.com/chainloop-dev/chainloop/releases">Changelog</a>
 </p>
 
+<p align="center"><sub>Last updated: 2026-10-16T13:15:50Z</sub></p>
+
 **Chainloop collects what happens across your software delivery, from the first prompt to the release, into one trusted graph. You define once what good means, as code, and Chainloop enforces it everywhere: every agent, every pipeline, every release.**
 
 Every AI coding session, pull request, build, SBOM, scan, and test report becomes a signed, timestamped record in your own registry or bucket. Each record links to the commit and release it belongs to. Rules live in git. Break one and the pipeline fails. The job prints every failing policy and its reason where the agent reads it. The agent fixes the work and pushes again, until Chainloop is happy.