updated README for pip-install

Bumps [actions/publish-action](https://github.com/actions/publish-action) from 0.3.0 to 0.4.0.
- [Commits](https://github.com/actions/publish-action/compare/v0.3.0...v0.4.0)

---
updated-dependencies:
- dependency-name: actions/publish-action
  dependency-version: 0.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

.github/workflows/release-new-action-version.yml

@@ -22,7 +22,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Update the ${{ env.TAG_NAME }} tag
-        uses: actions/publish-action@v0.3.0
+        uses: actions/publish-action@v0.4.0
         with:
           source-tag: ${{ env.TAG_NAME }}
           slack-webhook: ${{ secrets.SLACK_WEBHOOK }}

__tests__/data/requirements-linux.txt

@@ -7,6 +7,6 @@ Kivy-Garden==0.1.4
 packaging==20.7
 pdf2image==1.12.1
 Pygments==2.6.1
-requests==2.32.4
+requests==2.32.2
 urllib3==2.5.0
 xlrd==1.2.0

__tests__/data/requirements.txt

@@ -40,7 +40,7 @@ pyparsing==2.4.7; python_version >= '2.6' and python_version not in '3.0, 3.1, 3
 
 pywin32-ctypes==0.2.0
 
-requests==2.32.4
+requests==2.32.2
 
 urllib3==2.5.0
 

docs/advanced-usage.md

@@ -632,8 +632,8 @@ If the runner is not able to access github.com, any Python versions requested du
 The `allow-prereleases` flag defaults to `false`.
 If `allow-prereleases` is set to `true`, the action will allow falling back to pre-release versions of Python when a matching GA version of Python is not available.
 This allows for example to simplify reuse of `python-version` as an input of nox for pre-releases of Python by not requiring manipulation of the `3.y-dev` specifier.
-For CPython, `allow-prereleases` will only have effect for `x.y` version range (e.g. `3.12`).
-Let's say that python 3.12 is not generally available, the following workflow will fallback to the most recent pre-release of python 3.12:
+For CPython, `allow-prereleases` will only have effect for `x.y` version range (e.g. `3.14`).
+Let's say that in the past, when python 3.14 was not yet generally available, the following workflow would have fallback to the most recent pre-release of python 3.14:
 ```yaml
 jobs:
   test:
@@ -643,7 +643,7 @@ jobs:
       fail-fast: false
       matrix:
         os: [Ubuntu, Windows, macOS]
-        python_version: ["3.11", "3.12", "3.13"]
+        python_version: ["3.14"]
 
     steps:
       - uses: actions/checkout@v5
@@ -690,3 +690,5 @@ The `pip-install` input allows you to install dependencies as part of the Python
 ```
 > Note: This feature is intended for standard pip-based dependency installations.
 For complex workflows, or alternative package managers (e.g., poetry, pipenv), we recommend using separate steps to maintain clarity and flexibility.
+
+> The `pip-install` input mirrors the flexibility of a standard pip install command and supports most of its arguments.