From 38172c06ab58cd1f41fea4edd6f39f47b1f65b78 Mon Sep 17 00:00:00 2001 From: Polichinl Date: Sat, 27 Jun 2026 02:10:56 +0200 Subject: [PATCH] fix(ci): validate publish version against views-postprocessing, not pipeline-core (#10, C-09) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .github/workflows/publish_package.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/publish_package.yml b/.github/workflows/publish_package.yml index 5968e97..d599e16 100644 --- a/.github/workflows/publish_package.yml +++ b/.github/workflows/publish_package.yml @@ -30,7 +30,7 @@ jobs: - name: Validate Version run: | - latest_version=$(curl -s https://pypi.org/pypi/views-pipeline-core/json | jq -r .info.version) + latest_version=$(curl -s https://pypi.org/pypi/views-postprocessing/json | jq -r .info.version) new_version=$(python -c "import toml; print(toml.load('pyproject.toml')['tool']['poetry']['version'])") python -c "from packaging.version import parse; assert parse('$new_version') > parse('$latest_version'), 'Version must be higher than $latest_version'"