# Pipelock Release Notes: Release Posts and Upgrade Guides
Canonical URL: https://pipelab.org/learn/pipelock-release-notes/
Description: Pipelock release posts, newest first, with dates, what changed in each release, and the matching upgrade guides. The GitHub changelog covers every version.
Subtitle: Every Pipelock release post on this site in one place, newest first, with the matching upgrade guide.
Published: 2026-10-22



Most Pipelock releases have a post that explains what changed and why, and many also have an upgrade guide with the configuration and compatibility steps. This page lists every release post on this site, newest first. Some releases, including v2.7, v2.8, and v3.2, have no post here. The [Pipelock changelog on GitHub](https://github.com/pipelab-org/pipelock/blob/main/CHANGELOG.md) is the complete record of every version, including patch releases.

## Release posts

<table>
<thead><tr><th>Release</th><th>Date</th><th>What changed</th><th>Upgrade guide</th></tr></thead>
<tbody>
<tr>
<td><a href="/blog/pipelock-v370-release/index.md">Pipelock v3.7: Parallel Receipts and Filesystem Grants</a></td>
<td>2026-10-14</td>
<td>Pipelock v3.7 adds parallel signed receipts, filesystem grants, local MCP identity checks, exact destination grants, and stricter chain verification.</td>
<td><a href="/learn/pipelock-v370-upgrade/index.md">Pipelock v3.7 Upgrade</a></td>
</tr>
<tr>
<td><a href="/blog/pipelock-v360-release/index.md">Pipelock v3.6: Contained Agents You Can Watch and Check</a></td>
<td>2026-10-02</td>
<td>Pipelock v3.6 isolates contained agents in their own network namespace, signs what they changed, and lets credentials reach the services that issued them.</td>
<td><a href="/learn/pipelock-v360-upgrade/index.md">Pipelock v3.6 Upgrade Guide</a></td>
</tr>
<tr>
<td><a href="/blog/pipelock-v350-release/index.md">Pipelock v3.5: Native Agent Evidence Level Records</a></td>
<td>2026-09-01</td>
<td>Pipelock v3.5 writes Agent Evidence Level records natively, scans WebSocket control frames, and enforces the containment layers a launch applied.</td>
<td>None</td>
</tr>
<tr>
<td><a href="/blog/pipelock-v340-release/index.md">Pipelock v3.4: A Trust Label Can&#39;t Weaken a Block</a></td>
<td>2026-08-20</td>
<td>Pipelock v3.4 tightens MCP trust policy, scans media request bodies, hardens credential detection, and adds containment-aware upgrades.</td>
<td>None</td>
</tr>
<tr>
<td><a href="/blog/pipelock-v330-release/index.md">Pipelock v3.3: The Budget an Agent Can&#39;t Reset</a></td>
<td>2026-07-30</td>
<td>Pipelock v3.3 adds subject-keyed denial-of-wallet budgets, encoded-egress detection, opt-in audit-queue encryption, and SNI-required CONNECT.</td>
<td><a href="/learn/pipelock-v330-upgrade/index.md">Pipelock v3.3 Upgrade Guide</a></td>
</tr>
<tr>
<td><a href="/blog/pipelock-v310-release/index.md">Pipelock v3.1: Operator Evidence Gets Teeth</a></td>
<td>2026-07-13</td>
<td>Pipelock v3.1 adds an operator dashboard, free evidence viewer, strict receipt verification, SIEM/fleet readiness, and public benchmark-corpus updates.</td>
<td>None</td>
</tr>
<tr>
<td><a href="/blog/pipelock-v300-release/index.md">Pipelock v3.0: Fail Closed by Default</a></td>
<td>2026-06-23</td>
<td>Pipelock v3.0 hardens defaults to fail closed, adds signed self-update, provider-key DLP, and Conductor fleet operations.</td>
<td>None</td>
</tr>
<tr>
<td><a href="/blog/pipelock-v260-release/index.md">Pipelock v2.6: Inspection Moves to the Operation Boundary</a></td>
<td>2026-05-31</td>
<td>Pipelock v2.6 adds operation-level request policy, file-borne injection detection, hook-based agent inspection, and MCP hardening from NSA guidance.</td>
<td>None</td>
</tr>
<tr>
<td><a href="/blog/pipelock-v250-release/index.md">Pipelock v2.5.0: Portable Audit Evidence and Host Containment</a></td>
<td>2026-05-20</td>
<td>Pipelock v2.5.0 ships Audit Packet verifiers, host containment lifecycle commands, strict federation, MCP integrity, and IDE installers.</td>
<td><a href="/learn/pipelock-v250-upgrade/index.md">Pipelock v2.5 Upgrade</a></td>
</tr>
<tr>
<td><a href="/blog/pipelock-v240-release/index.md">Pipelock v2.4.0: Learn-and-Lock Contracts for Agent Traffic</a></td>
<td>2026-05-04</td>
<td>Pipelock v2.4.0 ships learn-and-lock contracts, block reason headers, inbound envelope verification, Gemini redaction, and health checks.</td>
<td><a href="/learn/pipelock-v240-upgrade/index.md">Pipelock v2.4 Upgrade</a></td>
</tr>
<tr>
<td><a href="/blog/pipelock-v230-release/index.md">Pipelock v2.3.0: Class-Preserving Redaction and Generic SSE Streaming</a></td>
<td>2026-04-24</td>
<td>Pipelock v2.3.0 ships class-preserving redaction across request transports, plus inline scanning for text/event-stream responses.</td>
<td><a href="/learn/pipelock-v230-upgrade/index.md">Pipelock v2.3 Upgrade</a></td>
</tr>
<tr>
<td><a href="/blog/pipelock-v220-release/index.md">Pipelock v2.2.0: Companion Proxies, Session Recovery, and Signed Mediation</a></td>
<td>2026-04-17</td>
<td>Pipelock v2.2.0 adds Kubernetes companion-proxy generation, session recovery, posture verification, signed mediation, and strict YAML validation.</td>
<td><a href="/learn/pipelock-v220-upgrade/index.md">Pipelock v2.2 Upgrade</a></td>
</tr>
</tbody>
</table>


## Reading older releases

Older posts describe behavior as it shipped in that version. Later releases changed some defaults: [v3.0](/blog/pipelock-v300-release/) moved enforcement to fail closed, for example. Check the newest upgrade guide before you copy a configuration from an older post.

## Further reading

- [Pipelock](/pipelock/): what the current release does
- [Install Pipelock](/install/)
- [Known limitations](/learn/known-limitations/)