Bump version: v2.17.0

docs/changelog.md

@@ -4,6 +4,23 @@ title: Changelog
 
 # Changelog
 
+### v2.17.0
+
+_11 March 2024_
+
+- 🌟 Adds the ability to inherit configuration in TOML overrides. This makes certain configurations much simpler. If you're overriding an option like `before-build` or `environment`, and you just want to add an  extra command or environment variable, you can just append (or prepend) to the previous config. See [the docs](https://cibuildwheel.pypa.io/en/stable/options/#inherit) for more information. (#1730)
+- 🌟 Adds official support for native arm64 macOS GitHub runners. To use them, just specify `macos-14` as an `os` of your job in your workflow file. You can also keep `macos-13` in your build matrix to build x86_64. Check out the new [GitHub Actions example config](https://cibuildwheel.pypa.io/en/stable/setup/#github-actions).
+- ✨ You no longer need to specify `--platform` to run cibuildwheel locally! Instead it will your platform automatically. This was a safety feature, no longer necessary. (#1727)
+- 🛠 Removed setuptools and wheel pinned versions. This only affects old-style projects without a `pyproject.toml`, projects with `pyproject.toml` are already getting fresh versions of their `build-system.requires` installed into an isolated environment. (#1725)
+- 🛠 Improve how the GitHub Action passes arguments (#1757)
+- 🛠 Remove a system-wide install of pipx in the GitHub Action (#1745)
+- 🐛 No longer will cibuildwheel override the PIP_CONSTRAINT environment variable when using the `build` frontend. Instead it will be extended. (#1675)
+- 🐛 Fix a bug where building and testing both x86_86 and arm64 wheels on the same runner caused the wrong architectures in the test environment (#1750)
+- 🐛 Fix a bug that prevented testing a CPython 3.8 wheel targeting macOS 11+ on x86_64 (#1768)
+- 📚 Moved the docs onto the official PyPA domain - they're now available at https://cibuildwheel.pypa.io . (#1775)
+- 📚 Docs and examples improvements (#1762, #1734)
+
+
 ### v2.16.5
 
 _30 January 2024_

docs/faq.md

@@ -142,7 +142,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.16.5
+uses: pypa/cibuildwheel@v2.17.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.
@@ -164,7 +164,7 @@ The second option, and the only one that supports other CI systems, is using a `
 
 ```bash
 # requirements-cibw.txt
-cibuildwheel==2.16.5
+cibuildwheel==2.17.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:
@@ -307,7 +307,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.16.5 --output-dir wheelhouse
+pipx run cibuildwheel==2.17.0 --output-dir wheelhouse
 pipx run twine upload wheelhouse/*.whl
 ```
 

docs/setup.md

@@ -154,7 +154,7 @@ To build Linux, Mac, and Windows wheels using GitHub Actions, create a `.github/
           - uses: actions/checkout@v4
 
           - name: Build wheels
-            run: pipx run cibuildwheel==2.16.5
+            run: pipx run cibuildwheel==2.17.0
 
           - uses: actions/upload-artifact@v4
             with:
@@ -191,7 +191,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.16.5
+            run: python -m pip install cibuildwheel==2.17.0
 
           - name: Build wheels
             run: python -m cibuildwheel --output-dir wheelhouse