chore(deps): update pypa/gh-action-pypi-publish action to v1.6.4 #166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.5.1
->v1.6.4
Release Notes
pypa/gh-action-pypi-publish
v1.6.4
Compare Source
oh, boi! again?
This is the last one tonight, promise! It fixes this embarrassing bug that was actually caught by the CI but got overlooked due to the lack of sleep.
TL;DR GH passed
$HOME
from the external env into the container and that tricked the Python'ssite
module to think that the home directory is elsewhere, adding non-existent paths to the env vars. See #115.Full Diff: pypa/gh-action-pypi-publish@v1.6.3...v1.6.4
v1.6.3
Compare Source
Another Release!? Why?
In https://github.com/pypa/gh-action-pypi-publish/issues/112#issuecomment-1340133013, it was discovered that passing a
$PATH
variable even breaks the shebang. So this version adds more safeguards to make sure it keeps working with a fully broken$PATH
.Full Diff: pypa/gh-action-pypi-publish@v1.6.2...v1.6.3
v1.6.2
Compare Source
What's Fixed
$PATH
and$PYTHONPATH
environment variables resilient to broken values passed from the host runner environment, which previously allowed the users to accidentally break the container's internal runtime as reported in https://github.com/pypa/gh-action-pypi-publish/issues/112Internal Maintenance Improvements
New Contributors
Full Diff: pypa/gh-action-pypi-publish@v1.6.1...v1.6.2
v1.6.1
Compare Source
What's happened?!
There was a sneaky bug in v1.6.0 which caused Twine to be outside the import path in the Python runtime. It is fixed in v1.6.1 by updating
$PYTHONPATH
to point to a correct location of the user-globalsite-packages/
directory.Full Diff: pypa/gh-action-pypi-publish@v1.6.0...v1.6.1
v1.6.0
Compare Source
Anything's changed?
The only update is that the Python runtime has been upgraded from 3.9 to 3.11. There are no functional changes in this release.
Full Changelog: pypa/gh-action-pypi-publish@v1.5.2...v1.6.0
v1.5.2
Compare Source
What's Improved
Full Diff: pypa/gh-action-pypi-publish@v1.5.1...v1.5.2
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.