From b457514c313d37748a23ed2c7432732108f7a0e6 Mon Sep 17 00:00:00 2001 From: LPW Date: Sat, 18 Apr 2026 00:32:23 -0700 Subject: [PATCH] chore(pipelock): bump chart default to v2.2.0, add CI scan badge (#1494) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Helm chart default pipelock.image.tag bumped from 2.0.0 to 2.2.0 (three minor releases behind latest) - README: pipelock CI scan status badge added to the existing badge row - charts/sure/README.md, docs/hosting/pipelock.md, pipelock.example.yaml: refreshed feature notes to reference the upstream changelog rather than pinning to a single version - compose.example.ai.yml: pin example comment bumped to :2.2.0 - Workflow pin (@v2) unchanged — floating major tag picks up 2.2.x --- README.md | 1 + charts/sure/CHANGELOG.md | 9 +++++++++ charts/sure/README.md | 6 +++--- charts/sure/values.yaml | 2 +- compose.example.ai.yml | 2 +- docs/hosting/pipelock.md | 4 ++-- pipelock.example.yaml | 8 +++++--- 7 files changed, 22 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index fe45b8bbb..94f678d84 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,7 @@ [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/we-promise/sure) [![View performance data on Skylight](https://badges.skylight.io/typical/s6PEZSKwcklL.svg)](https://oss.skylight.io/app/applications/s6PEZSKwcklL) [![Dosu](https://raw.githubusercontent.com/dosu-ai/assets/main/dosu-badge.svg)](https://app.dosu.dev/a72bdcfd-15f5-4edc-bd85-ea0daa6c3adc/ask) +[![Pipelock Security Scan](https://github.com/we-promise/sure/actions/workflows/pipelock.yml/badge.svg)](https://github.com/we-promise/sure/actions/workflows/pipelock.yml) sure_shot diff --git a/charts/sure/CHANGELOG.md b/charts/sure/CHANGELOG.md index 628fcdce7..0abee238d 100644 --- a/charts/sure/CHANGELOG.md +++ b/charts/sure/CHANGELOG.md @@ -5,6 +5,15 @@ All notable changes to the Sure Helm chart will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). +## [Unreleased] + +### Changed +- Bumped `pipelock.image.tag` from `2.0.0` to `2.2.0` (three minor releases behind latest). Floating `@v2` CI action pin picks up patch/minor updates automatically. +- Refreshed pipelock feature notes in the chart README, `docs/hosting/pipelock.md`, and `pipelock.example.yaml` to reference the upstream changelog instead of a single version. + +### Added +- README: CI scan status badge for the pipelock workflow. + ## [0.6.9-alpha] - 2026-03-24 ### Changed diff --git a/charts/sure/README.md b/charts/sure/README.md index 28b8e164f..73d5eb464 100644 --- a/charts/sure/README.md +++ b/charts/sure/README.md @@ -645,7 +645,7 @@ hpa: - **Forward proxy** (port 8888): Scans outbound HTTPS from Faraday-based AI clients. Auto-injected via `HTTPS_PROXY` env vars when enabled. - **MCP reverse proxy** (port 8889): Scans inbound MCP traffic from external AI assistants. -v2.0 adds enhanced tool poisoning detection (full JSON schema scanning), per-read kill switch preemption on long-lived connections, trusted domain allowlisting, and MCP tool redirect profiles. Process sandboxing and attack simulation are also available via `extraConfig` and CLI. +Recent pipelock releases add enhanced tool poisoning detection (full JSON schema scanning), per-read kill switch preemption, trusted domain allowlisting, MCP tool redirect profiles, signed action receipts, per-pattern DLP warn mode, and the `pipelock posture verify` / `pipelock session` CLIs. Process sandboxing and attack simulation are also available via `extraConfig` and CLI. See the [pipelock changelog](https://github.com/luckyPipewrench/pipelock/releases) for details. ### Enabling Pipelock @@ -653,7 +653,7 @@ v2.0 adds enhanced tool poisoning detection (full JSON schema scanning), per-rea pipelock: enabled: true image: - tag: "2.0.0" + tag: "2.2.0" mode: balanced # strict, balanced, or audit ``` @@ -685,7 +685,7 @@ pipelock: ### Validating your config -Pipelock v2.0 includes two CLI tools for config validation: +Pipelock includes CLI tools for config validation: ```bash # Run 24 synthetic attack scenarios against your config diff --git a/charts/sure/values.yaml b/charts/sure/values.yaml index 7836b12fb..f4b54f69e 100644 --- a/charts/sure/values.yaml +++ b/charts/sure/values.yaml @@ -497,7 +497,7 @@ pipelock: enabled: false image: repository: ghcr.io/luckypipewrench/pipelock - tag: "2.0.0" + tag: "2.2.0" pullPolicy: IfNotPresent imagePullSecrets: [] replicas: 1 diff --git a/compose.example.ai.yml b/compose.example.ai.yml index a1de3b6e8..7c79178f7 100644 --- a/compose.example.ai.yml +++ b/compose.example.ai.yml @@ -112,7 +112,7 @@ x-rails-env: &rails_env services: pipelock: - image: ghcr.io/luckypipewrench/pipelock:latest # pin to a specific version (e.g., :2.0.0) for production + image: ghcr.io/luckypipewrench/pipelock:latest # pin to a specific version (e.g., :2.2.0) for production container_name: pipelock hostname: pipelock restart: unless-stopped diff --git a/docs/hosting/pipelock.md b/docs/hosting/pipelock.md index b1f039eeb..08c14fb13 100644 --- a/docs/hosting/pipelock.md +++ b/docs/hosting/pipelock.md @@ -77,13 +77,13 @@ Enable Pipelock in your Helm values: pipelock: enabled: true image: - tag: "2.0.0" + tag: "2.2.0" mode: balanced ``` This creates a separate Deployment, Service, and ConfigMap. The chart auto-injects `HTTPS_PROXY`/`HTTP_PROXY`/`NO_PROXY` into web and worker pods. -v2.0 adds trusted domain allowlisting, MCP tool redirect profiles, enhanced tool poisoning detection (full JSON schema scanning), and per-read kill switch preemption on long-lived connections. Process sandboxing and attack simulation are also available via `extraConfig` and CLI. +Recent pipelock releases add trusted domain allowlisting, MCP tool redirect profiles, enhanced tool poisoning detection (full JSON schema scanning), per-read kill switch preemption, signed action receipts, per-pattern DLP warn mode, and the `pipelock posture verify` / `pipelock session` CLI commands. See the [pipelock changelog](https://github.com/luckyPipewrench/pipelock/releases) for details. ### Exposing MCP to external agents (Kubernetes) diff --git a/pipelock.example.yaml b/pipelock.example.yaml index 2458f834f..ee77d162f 100644 --- a/pipelock.example.yaml +++ b/pipelock.example.yaml @@ -1,8 +1,10 @@ # Pipelock configuration for Docker Compose # See https://github.com/luckyPipewrench/pipelock for full options. # -# New in v2.0: trusted_domains, redirect profiles, attack simulation, -# security scoring, process sandbox, and enhanced tool poisoning detection. +# Recent additions: trusted_domains, redirect profiles, attack simulation, +# security scoring, process sandbox, enhanced tool poisoning detection, signed +# action receipts, per-pattern DLP warn mode, and the `pipelock posture verify` +# / `pipelock session` CLIs. # Run `pipelock simulate --config ` to test your config against 24 attack scenarios. # Run `pipelock audit score --config ` for a security posture score (0-100). @@ -54,7 +56,7 @@ mcp_tool_scanning: mcp_tool_policy: enabled: false action: warn - # Redirect profiles (v2.0): route matched tool calls to audited handler programs + # Redirect profiles: route matched tool calls to audited handler programs # instead of blocking. The handler returns a synthetic MCP response. # redirect_profiles: # safe-fetch: