From d25f5126d3f4ce787c4485f1f7a33c164441fa72 Mon Sep 17 00:00:00 2001 From: Polichinl Date: Sat, 19 Sep 2026 04:41:05 +0200 Subject: [PATCH] =?UTF-8?q?release:=200.3.4=20=E2=80=94=20co-resolution=20?= =?UTF-8?q?release=20for=20views-pipeline-core=203.3.0?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Version bump only; every pin, test and doc change is already on main (#291–#298). Why now: PyPI 0.3.3's immutable metadata pins views-evaluation<2.0.0, while vpc 3.3.0 requires >=2.0.0 — the pair cannot co-install, and a plain `pip install views-reporting` silently backtracks to vpc 3.2.0, whose reporting stage blanks every baseline/constituent row (C-215). 0.3.4 carries vpc>=3.3.0 + views-evaluation>=2.0.0 so a fresh install gets the fixed stage. Simon-approved 2026-09-19 (Cluster H's recorded trigger: "the day vpc actually pins ^2.0.0"). Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01N7YBtiS2kSVj27spMKDYfh --- pyproject.toml | 2 +- uv.lock | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/pyproject.toml b/pyproject.toml index 8e3dc2d..5a5b214 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,6 +1,6 @@ [project] name = "views-reporting" -version = "0.3.3" +version = "0.3.4" description = "Visualization, reporting, statistics, and mapping for the VIEWS conflict forecasting platform." authors = [ { name = "Dylan Pinheiro", email = "dylpin@prio.org" }, diff --git a/uv.lock b/uv.lock index df341a0..ec07dbe 100644 --- a/uv.lock +++ b/uv.lock @@ -2398,7 +2398,7 @@ wheels = [ [[package]] name = "views-reporting" -version = "0.3.3" +version = "0.3.4" source = { editable = "." } dependencies = [ { name = "geopandas", marker = "sys_platform == 'darwin' or sys_platform == 'linux'" },