Bump version: v3.2.0

docs/changelog.md

@@ -4,6 +4,17 @@ title: Changelog
 
 # Changelog
 
+### v3.2.0
+
+_22 September 2025_
+
+- ✨ Adds GraalPy v25 (Python 3.12) support (#2597)
+- 🛠 Update to CPython 3.14.0rc3 (#2602)
+- 🛠 Adds CPython 3.14.0 prerelease support for Android, and a number of improvements to Android builds (#2568, #2591)
+- 🛠 Improvements to testing on Android, passing environment markers when installing the venv, and providing more debug output when build-verbosity is set (#2575)
+- ⚠️ PyPy 3.10 was moved to `pypy-eol` in the `enable` option, as it is now end-of-life. (#2521)
+- 📚 Docs improvements (#2574, #2601, #2598)
+
 ### v3.1.4
 
 _19 August 2025_

docs/faq.md

@@ -110,7 +110,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.1.4
+uses: pypa/cibuildwheel@v3.2.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.
@@ -132,7 +132,7 @@ The second option, and the only one that supports other CI systems, is using a `
 
 ```bash
 # requirements-cibw.txt
-cibuildwheel==3.1.4
+cibuildwheel==3.2.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:
@@ -297,7 +297,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.1.4 --output-dir wheelhouse
+pipx run cibuildwheel==3.2.0 --output-dir wheelhouse
 pipx run twine upload wheelhouse/*.whl
 ```