From a35d6d61780d4517add76adb97b99f38d3f04844 Mon Sep 17 00:00:00 2001 From: iruzen-dono Date: Thu, 12 Nov 2026 20:28:30 +0000 Subject: [PATCH 1/2] fix(deps): require cmdstanpy 1.3.2 so Windows source builds stop fetching a retired Rtools URL `cmdstanpy` 1.3.0 downloads the RTools 4.0 installer from `cran.r-project.org/bin/windows/Rtools/rtools40-x86_64.exe`, which CRAN retired (HTTP 404). 1.3.2 uses `cran-archive.r-project.org`, which still serves it. The metadata asked for `>=1.0.4`, so a stale pip cache on the runner resolved 1.3.0 and every Windows source/editable build died while compiling the Stan model, before a single test ran. The floor moves to `>=1.3.2` in both places the file declares it: the build system's `requires` (used by the editable install that failed) and the project dependencies. 1.3.2 supports Python >=3.9, so the `>=3.10` this project already requires is unaffected. The Actions-cache side of the report is a maintainer call; this change only makes the metadata stop permitting the broken release. --- python/pyproject.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/python/pyproject.toml b/python/pyproject.toml index d9e58cac8..025b35b82 100644 --- a/python/pyproject.toml +++ b/python/pyproject.toml @@ -2,7 +2,7 @@ requires = [ "setuptools>=64", "wheel", - "cmdstanpy>=1.0.4", + "cmdstanpy>=1.3.2", ] build-backend = "setuptools.build_meta" @@ -13,7 +13,7 @@ description = "Automatic Forecasting Procedure" readme = "README.md" requires-python = ">=3.10" dependencies = [ - "cmdstanpy>=1.0.4", + "cmdstanpy>=1.3.2", "numpy>=1.21.6", "matplotlib>=3.5.3", "pandas>=1.3.5", From cac09b65b92bdf81ce5931b7b48dc7d595e15e26 Mon Sep 17 00:00:00 2001 From: iruzen-dono Date: Thu, 12 Nov 2026 20:44:13 +0000 Subject: [PATCH 2/2] chore: retrigger the CLA check after signing