Bump version: v3.0.0rc2

docs/changelog.md

@@ -19,6 +19,12 @@ If you've used previous versions of the beta:
 - ⚠️ 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).
 
+#### v3.0.0rc2
+
+_6 June 2025_
+
+- 🛠 Updates to dependencies including Pyodide, python-build-standalone, and iOS support package. (#2449)
+
 #### v3.0.0rc1
 
 _5 June 2025_

docs/faq.md

@@ -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.0rc1
+uses: pypa/cibuildwheel@v3.0.0rc2
 ```
 
 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.0rc1
+cibuildwheel==3.0.0rc2
 ```
 
 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.0rc1 --output-dir wheelhouse
+pipx run cibuildwheel==3.0.0rc2 --output-dir wheelhouse
 pipx run twine upload wheelhouse/*.whl
 ```