Bump version: v2.11.0
This commit is contained in:
@@ -4,6 +4,19 @@ title: Changelog
|
||||
|
||||
# Changelog
|
||||
|
||||
### v2.11.0
|
||||
|
||||
_13 October 2022_
|
||||
|
||||
- 🌟 Adds support for cross-compiling Windows ARM64 wheels. To use this feature, add `ARM64` to the [CIBW_ARCHS](https://cibuildwheel.readthedocs.io/en/stable/options/#archs) option on a Windows Intel runner. (#1144)
|
||||
- ✨ Adds support for building Linux aarch64 wheels on Circle CI. (#1307)
|
||||
- ✨ Adds support for building Windows wheels on Gitlab CI. (#1295)
|
||||
- ✨ Adds support for building Linux aarch64 wheels under emulation on Gitlab CI. (#1295)
|
||||
- ✨ Adds the ability to test `cp38-macosx_arm64` wheels on a native arm64 runner. To do this, you'll need to preinstall the (experimental) [universal2 version of CPython 3.8](https://www.python.org/ftp/python/3.8.10/python-3.8.10-macos11.pkg) on your arm64 runner before invoking cibuildwheel. Note: it is not recommended to build x86_64 wheels with this setup, your wheels will have limited compatibility wrt macOS versions. (#1283)
|
||||
- 🛠 Improved error messages when using custom Docker images and Python cannot be found at the correct path. (#1298)
|
||||
- 📚 Sample configs for Azure Pipelines and Travis CI updated (#1296)
|
||||
- 📚 Other docs improvements - including more information about using Homebrew for build dependencies (#1290)
|
||||
|
||||
### v2.10.2
|
||||
|
||||
_25 September 2022_
|
||||
|
||||
+3
-3
@@ -143,7 +143,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@v2.10.2
|
||||
uses: pypa/cibuildwheel@v2.11.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.
|
||||
@@ -165,7 +165,7 @@ The second option, and the only one that supports other CI systems, is using a `
|
||||
|
||||
```bash
|
||||
# requirements-cibw.txt
|
||||
cibuildwheel==2.10.2
|
||||
cibuildwheel==2.11.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:
|
||||
@@ -309,7 +309,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==2.10.2 --output-dir wheelhouse
|
||||
pipx run cibuildwheel==2.11.0 --output-dir wheelhouse
|
||||
pipx run twine upload wheelhouse/*.whl
|
||||
```
|
||||
|
||||
|
||||
+2
-2
@@ -184,7 +184,7 @@ To build Linux, Mac, and Windows wheels using GitHub Actions, create a `.github/
|
||||
- uses: actions/checkout@v3
|
||||
|
||||
- name: Build wheels
|
||||
run: pipx run cibuildwheel==2.10.2
|
||||
run: pipx run cibuildwheel==2.11.0
|
||||
|
||||
- uses: actions/upload-artifact@v3
|
||||
with:
|
||||
@@ -219,7 +219,7 @@ To build Linux, Mac, and Windows wheels using GitHub Actions, create a `.github/
|
||||
- uses: actions/setup-python@v3
|
||||
|
||||
- name: Install cibuildwheel
|
||||
run: python -m pip install cibuildwheel==2.10.2
|
||||
run: python -m pip install cibuildwheel==2.11.0
|
||||
|
||||
- name: Build wheels
|
||||
run: python -m cibuildwheel --output-dir wheelhouse
|
||||
|
||||
Reference in New Issue
Block a user