From 6e1813b5e3e6e4c71e491d6d89407731eac9e07b Mon Sep 17 00:00:00 2001 From: Binay Date: Tue, 18 Aug 2026 20:10:42 -0400 Subject: [PATCH] chore: bump the signetry-core pin to v0.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit v0.7.0 shipped Kotlin detection, Go SSRF, Go/Java path traversal, PHP XXE, the Aider executor and the SSRF precision fixes. These references still installed v0.6.0, so anything following them got an engine several rules behind. CHANGELOG entries are deliberately left at v0.6.0 — they record what a past release pinned and are not live install instructions. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e95a046..b82645b 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Two ways to govern coding-agent changes in Cursor with ## Prerequisite ```bash -pip install "signetry-core @ git+https://github.com/Signetry/core@v0.6.0" +pip install "signetry-core @ git+https://github.com/Signetry/core@v0.7.0" ``` Add a `.signetry/admission.yaml` to your repo declaring allowed/forbidden paths,