mirror of
https://github.com/we-promise/sure
synced 2026-04-25 17:15:07 +02:00
chore(pipelock): bump chart default to v2.2.0, add CI scan badge (#1494)
- 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
This commit is contained in:
@@ -1,6 +1,7 @@
|
||||
[](https://deepwiki.com/we-promise/sure)
|
||||
[](https://oss.skylight.io/app/applications/s6PEZSKwcklL)
|
||||
[](https://app.dosu.dev/a72bdcfd-15f5-4edc-bd85-ea0daa6c3adc/ask)
|
||||
[](https://github.com/we-promise/sure/actions/workflows/pipelock.yml)
|
||||
|
||||
<img width="1270" height="1140" alt="sure_shot" src="https://github.com/user-attachments/assets/9c6e03cc-3490-40ab-9a68-52e042c51293" />
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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)
|
||||
|
||||
|
||||
@@ -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 <file>` to test your config against 24 attack scenarios.
|
||||
# Run `pipelock audit score --config <file>` 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:
|
||||
|
||||
Reference in New Issue
Block a user