Skip to content

release: 0.3.4 — co-resolution release for views-pipeline-core 3.3.0 - #299

Merged
Polichinel merged 1 commit into
developmentfrom
release/0.3.4
Sep 19, 2026
Merged

Polichinel merged 1 commit into
developmentfrom
release/0.3.4

Conversation

@Polichinel

Copy link
Copy Markdown
Contributor

Version bump only (0.3.3 → 0.3.4; lock re-stamped). Everything else a release needs is already on main (#291–#298).

Why now: PyPI 0.3.3's immutable metadata pins views-evaluation<2.0.0; vpc 3.3.0 requires >=2.0.0. Verified: the pair cannot co-install, and a plain pip install views-reporting today silently backtracks to vpc 3.2.0 — the stage that blanks every baseline row. 0.3.4 carries vpc>=3.3.0 + views-evaluation>=2.0.0 so a fresh install gets the fixed stage. This is Cluster H's recorded trigger ("the day vpc pins ^2.0.0"), approved by Simon today.

Suite 443 green. Release + Trusted-Publishing publish follows the main merge.

🤖 Generated with Claude Code

https://claude.ai/code/session_01N7YBtiS2kSVj27spMKDYfh

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) <[email protected]>
Claude-Session: https://claude.ai/code/session_01N7YBtiS2kSVj27spMKDYfh
@Polichinel
Polichinel merged commit 830aaef into development Sep 19, 2026
1 check passed
@Polichinel
Polichinel deleted the release/0.3.4 branch September 19, 2026 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant