splunk / splunk-sdk-python

Splunk Software Development Kit for Python
http://dev.splunk.com
Apache License 2.0
698 stars 370 forks source link

Bump pypa/gh-action-pypi-publish from 1.3.1 to 1.7.1 #519

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps pypa/gh-action-pypi-publish from 1.3.1 to 1.7.1.

Release notes

Sourced from pypa/gh-action-pypi-publish's releases.

v1.7.1

Regression?

There was a small setback with v1.7.0 — the snake_case fallbacks didn't work because the check for the kebab-case env vars with default values set was always truthy. This bugfix release promptly fixes that.

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.7.0...v1.7.1

v1.7.0

What should I care about?

TL;DR The action input names have been converted to use kebab-case and marked deprecated. But the old names still work.

This is made to align the public API with the de-facto conventions in the ecosystem. We've used snake_case names, which the maintainer considers a historical mistake. New kebab-case inputs will make the end-users' workflows look more consistent and and visually distinguishable from other identifiers one may encounter in YAML.

There is no timeline for removing the old names, but it will happen in v3 or later versions of the action. If the maintainer doesn't forget to do this, that is.

The patch is here: pypa/gh-action-pypi-publish#125.

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.6.5...v1.7.0

v1.6.5

What's Changed

  • Added an explicit warning when the password passed into the action is empty — thanks @​colindean

New Contributors

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.6.4...v1.6.5

v1.6.4

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's site module to think that the home directory is elsewhere, adding non-existent paths to the env vars. See #115.

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.6.3...v1.6.4

v1.6.3

Another Release!? Why?

In pypa/gh-action-pypi-publish#112, 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: https://github.com/pypa/gh-action-pypi-publish/compare/v1.6.2...v1.6.3

v1.6.2

What's Fixed

  • Made the $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 pypa/gh-action-pypi-publish#112

Internal Maintenance Improvements

... (truncated)

Commits
  • 22b4d1f 🐛 Make kebab options fall back for snake_case
  • 7104b6e Merge branch 'maintenance/kebab-case-inputs' into unstable/v1
  • f131721 🎨 Convert action inputs to use kebab-case
  • 32b5e93 Merge pull request #122 from colindean/empty-token
  • efcb9ba 🎨 Warn about empty password/token action input
  • d2ce3ec ⇪ Bump isort to v5.12.0
  • 0eaf3a1 Merge pull request #121 from pypa/dependabot/pip/requirements/cryptography-39...
  • 6a2da9b Bump cryptography from 38.0.4 to 39.0.1 in /requirements
  • 7eb3b70 Merge pull request #119 from pypa/pre-commit-ci-update-config
  • 91e6121 Revert WPS flake8 hook version to 4.0.1
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #520.