Skip to content

fix(ci): validate publish version against views-postprocessing, not pipeline-core (#10) - #67

Merged
Polichinel merged 1 commit into
developmentfrom
fix/publish-version-check-10
Jun 27, 2026
Merged

Polichinel merged 1 commit into
developmentfrom
fix/publish-version-check-10

Conversation

@Polichinel

Copy link
Copy Markdown
Collaborator

Closes #10 (C-09). The publish workflow's version gate (publish_package.yml:33) fetched views-pipeline-core's latest PyPI version and compared the new views-postprocessing version against it — the wrong package. Pointed it at views-postprocessing's own PyPI metadata.

One-line CI fix; no runtime impact.

Closes #10

🤖 Generated with Claude Code

…ipeline-core (#10, C-09)

The publish workflow's version gate fetched the latest version of
views-pipeline-core from PyPI and compared the new views-postprocessing version
against it — the wrong package. A release could pass or fail the monotonicity
check for unrelated reasons. Point the check at views-postprocessing's own PyPI
metadata.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Polichinel
Polichinel merged commit 75d6307 into development Jun 27, 2026
4 checks passed
@Polichinel
Polichinel deleted the fix/publish-version-check-10 branch June 27, 2026 00:13
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