Hongru/cibuildwheel
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Bump version: v3.0.0rc3

Browse Source
This commit is contained in:
Henry Schreiner
2025-06-11 00:57:01 -04:00
parent 1b9a56e014
commit 3c5ff09888
18 changed files with 45 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/changelog.md
+9
View File
@@ -18,6 +18,15 @@ If you've used previous versions of the beta:
- ⚠️ Previous betas of v3.0 changed the working directory for tests. This has been rolled back to the v2.x behaviour, so you might need to change configs if you adapted to the beta 1 or 2 behaviour. See [issue #2406](https://github.com/pypa/cibuildwheel/issues/2406) for more information.
- ⚠️ GraalPy shipped with the identifier `gp242-*` in previous betas, this has been changed to `gp311_242-*` to be consistent with other interpreters, and to fix a bug with GraalPy and project requires-python detection. If you were using GraalPy, you might need to update your config to use the new identifier.
- ⚠️ `test-sources` now uses `project` directory instead of the `package` directory (matching the docs).
- ⚠️ 32-bit linux builds were removed from `"auto"` (the default), now require `"auto32"` or explicit archs, as modern manylinux images (including our new default) do not support them.
#### v3.0.0rc3
_11 June 2025_
- 🛠 32-bit linux builds removed from `"auto"`, requires explicit `"auto32"`. (#2458)
- 📚 Warn that `pyodide-version` is experimental. (#2450)
#### v3.0.0rc2
docs/faq.md
+3 -3
View File
@@ -60,7 +60,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@v3.0.0rc2
uses: pypa/cibuildwheel@v3.0.0rc3
```
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.
@@ -82,7 +82,7 @@ The second option, and the only one that supports other CI systems, is using a `
```bash
# requirements-cibw.txt
cibuildwheel==3.0.0rc2
cibuildwheel==3.0.0rc3
```
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:
@@ -247,7 +247,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==3.0.0rc2 --output-dir wheelhouse
pipx run cibuildwheel==3.0.0rc3 --output-dir wheelhouse
pipx run twine upload wheelhouse/*.whl
```