From dbf00e3223b0a7a357a53449427dc23d23293bd9 Mon Sep 17 00:00:00 2001 From: Test Date: Mon, 16 Nov 2026 21:53:40 -0500 Subject: [PATCH] chore(release): specfuse-loop 0.33.2 Co-Authored-By: Claude Opus 5.5 --- .specfuse/VERSION | 2 +- CHANGELOG.md | 6 ++++++ .../3592-specfuse-monitor-run-azure-failure-signa.md | 5 ----- pyproject.toml | 2 +- specfuse/loop/data/VERSION | 2 +- specfuse/loop/loop.py | 2 +- 6 files changed, 10 insertions(+), 9 deletions(-) delete mode 100644 changelog.d/3592-specfuse-monitor-run-azure-failure-signa.md diff --git a/.specfuse/VERSION b/.specfuse/VERSION index 8df3f459..c9ec1d54 100644 --- a/.specfuse/VERSION +++ b/.specfuse/VERSION @@ -1 +1 @@ -0.33.1 +0.33.2 diff --git a/CHANGELOG.md b/CHANGELOG.md index 9f9782d7..d74b7d11 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -26,6 +26,12 @@ Entries below cover only work landing from FEAT-2026-0064 onward. ## [Unreleased] +## [0.33.2+umbrella.0.17.0] - 2026-11-16 + +### Fixed + +- `specfuse monitor run`: Azure failure signatures no longer carry per-occurrence tokens — a GUID followed by `_` (the Service Bus `TrackingId:_B4` shape), `TrackingId`/`SystemTracker`/`Reference`/`LockToken` values, HTTP `Date:` headers, and stack traces embedded by Functions host wrapper exceptions are normalized away, so repeat occurrences of one failure land on one issue instead of one each. Existing findings whose signature changes are filed once more under the new signature. (#3592) + ## [0.33.1+umbrella.0.17.0] - 2026-11-15 ### Fixed diff --git a/changelog.d/3592-specfuse-monitor-run-azure-failure-signa.md b/changelog.d/3592-specfuse-monitor-run-azure-failure-signa.md deleted file mode 100644 index 53a8b296..00000000 --- a/changelog.d/3592-specfuse-monitor-run-azure-failure-signa.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -class: fixed -trace: #3592 ---- -`specfuse monitor run`: Azure failure signatures no longer carry per-occurrence tokens — a GUID followed by `_` (the Service Bus `TrackingId:_B4` shape), `TrackingId`/`SystemTracker`/`Reference`/`LockToken` values, HTTP `Date:` headers, and stack traces embedded by Functions host wrapper exceptions are normalized away, so repeat occurrences of one failure land on one issue instead of one each. Existing findings whose signature changes are filed once more under the new signature. diff --git a/pyproject.toml b/pyproject.toml index cad6f304..07bbf72d 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta" [project] name = "specfuse-loop" -version = "0.33.1" +version = "0.33.2" description = "Local-first executor for the Specfuse Plan + Work Unit gate-cycle methodology." readme = "README.md" requires-python = ">=3.10" diff --git a/specfuse/loop/data/VERSION b/specfuse/loop/data/VERSION index 8df3f459..c9ec1d54 100644 --- a/specfuse/loop/data/VERSION +++ b/specfuse/loop/data/VERSION @@ -1 +1 @@ -0.33.1 +0.33.2 diff --git a/specfuse/loop/loop.py b/specfuse/loop/loop.py index 16f1cef3..17e32d96 100644 --- a/specfuse/loop/loop.py +++ b/specfuse/loop/loop.py @@ -135,7 +135,7 @@ REPO_ROOT = SPECFUSE_DIR.parent FEATURES_DIR = SPECFUSE_DIR / "features" VERIFICATION_PATH = SPECFUSE_DIR / "verification.yml" -DRIVER_VERSION = "0.33.1" +DRIVER_VERSION = "0.33.2" # Oldest scaffold layout this driver can drive. init.sh stamps the scaffold's own # version into `.specfuse/VERSION`; check_scaffold_version() fails loud at startup if # the consumer's scaffold is older than this, pointing at `specfuse upgrade`. Bump