Bump version: v4.1.0

This commit is contained in:
Joe Rickerby
2026-06-12 17:02:22 +01:00
parent 14a3c3a226
commit 2947353127
13 changed files with 41 additions and 35 deletions
+10
View File
@@ -5,6 +5,16 @@ ref: changelog
# Changelog
### v4.1.0
_12 June 2026_
- ✨ Updates Pyodide to the final 314.0.0 release, so Pyodide 3.14 wheels now build by default without the `pyodide-prerelease` [`enable`](https://cibuildwheel.pypa.io/en/stable/options/#enable) flag. (#2906)
- 🐛 Raises clear errors when a build produces no wheel, instead of failing later with a confusing message (#2909)
- 🛠 Speeds up CLI startup through lazy imports on Python 3.15 (#2797)
- 📚 Adds an FAQ section on caching cibuildwheel's downloaded tools with `CIBW_CACHE_PATH` (#2842)
- 📚 Documentation improvements: clarifies which shell is used for command options, clarifies environment variable precedence, and fixes a dead Pyodide env info link (#2904, #2905, #2911)
### v4.0.0
_7 June 2026_
+3 -3
View File
@@ -158,7 +158,7 @@ There are two suggested methods for keeping cibuildwheel up to date that instead
If you use GitHub Actions for builds, you can use cibuildwheel as an action:
```yaml
uses: pypa/cibuildwheel@v4.0.0
uses: pypa/cibuildwheel@v4.1.0
```
This is a composite step that just runs cibuildwheel using pipx. You can set command-line options as `with:` parameters, and use `env:` as normal.
@@ -183,7 +183,7 @@ The second option, and the only one that supports other CI systems, is using a `
```bash
# requirements-cibw.txt
cibuildwheel==4.0.0
cibuildwheel==4.1.0
```
Then your install step would have `python -m pip install -r requirements-cibw.txt` in it. Your `.github/dependabot.yml` file could look like this:
@@ -402,7 +402,7 @@ Solutions to this vary, but the simplest is to use pipx:
# most runners have pipx preinstalled, but in case you don't
python3 -m pip install pipx
pipx run cibuildwheel==4.0.0 --output-dir wheelhouse
pipx run cibuildwheel==4.1.0 --output-dir wheelhouse
pipx run twine upload wheelhouse/*.whl
```