⬆ Bump pypa/gh-action-pypi-publish from 1.4.2 to 1.10.3

[dependabot]

Bumps pypa/gh-action-pypi-publish from 1.4.2 to 1.10.3.

Release notes

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

v1.10.3

💅 Cosmetic Output Improvements

In #270, @​facutuesca💰 made a follow-up to their previous PR #250, making the hints show up more granularly. This effectively makes sure that the suggestion to enable Trusted Publishing does not get displayed when it's already in use. It also makes the message nicer in a few places on the UI.

🛠️ Internal Dependencies

@​mosfet80💰 updated a few internal linter versions in #266, #267, and #271, no user impact. This is usually automated otherwise.

💪 New Contributors

• @​mosfet80 made their first contribution in pypa/gh-action-pypi-publish#266

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.2...v1.10.3

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

v1.10.2

💅 Cosmetic Output Improvements

In #250 and #258, @​facutuesca💰 added a nudge message with a magic link to pre-fill the creation of new Trusted Publishers configurations on PyPI. The users are now suggested to configure tokenless publishing by clicking a link printed in the job summary when it's detected that they publish to PyPI or TestPyPI. Just like magic! 🦄

🛠️ Internal Dependencies

@​woodruffw💰 bumped pypi-attestations to v0.0.12 in #262, hopefully fixing #263. 🤞 Nah.. that wasn't it.

[!TIP] Please keep in mind that reusable workflows are not yet supported, even though they sometimes work, mostly by accident.

💪 New Contributors

@​facutuesca made their first contribution in pypa/gh-action-pypi-publish#258

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.1...v1.10.2

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

🙏 Special Thanks to @​henryiii💰 for promptly pointing up possible fixes for #263.

v1.10.1

🚑🔏 Oopsie... We missed a tiny bug in the attestations feature the other day

The problem was that the distribution file validity check was failing on any valid distribution being present and ready to be signed. What a silly mistake! It's now been fixed via pypa/gh-action-pypi-publish@0ab0b79, though. So everything's good!

-- @​webknjaz💰

[!IMPORTANT] ✨ Despite this minor hiccup, we invite you to still opt into trying this feature out early. It can be enabled like this:

  with:
    attestations: true

Leave feedback in the v1.10.0 release discussion or the PR.

... (truncated)

Commits

• f760068 Merge pull request #271 from mosfet80/patch-3
• 6edc294 Fix node.js v16 deprecation self-smoke-test-action.yml
• 85a5a80 Merge pull request #270 from trail-of-forks/fix-magic-link-summary
• 954318b Merge pull request #267 from mosfet80/patch-2
• 24791c7 Merge pull request #266 from mosfet80/patch-1
• d8c8948 Fix magic link nudge formatting in job summary
• a1ce384 Check for Trusted Publishing in magic link logic
• 00b87c8 Update check-jsonschema and pre-commit libs
• a571f1e Update pylint lib
• 897895f Merge pull request #262 from trail-of-forks/ww/bump-attestations-req
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

Summary by Sourcery

Bump the pypa/gh-action-pypi-publish GitHub Action from version 1.4.2 to 1.10.3 in the CI workflow to incorporate the latest improvements and fixes.

CI:

• Update the GitHub Action for PyPI publishing from version 1.4.2 to 1.10.3 in the CI workflow configuration.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the pypa/gh-action-pypi-publish GitHub Action from version 1.4.2 to 1.10.3 in the project's Python package publishing workflow. The update includes several improvements and bug fixes to the PyPI publishing process.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Update pypa/gh-action-pypi-publish GitHub Action version	Changed the version hash from 27b31702a0e7fc50959f5ad993c78deac1bdfc29 to f7600683efdcb7656dec5b29656edb7bc586e597 Implicitly updated from version 1.4.2 to 1.10.3	.github/workflows/python-publish.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: build (3.10)

Failed stage: Check Python code type [❌]

Failure summary: The action failed because there was an error while trying to get the requirements to build a wheel for the package matplotlib. The error occurred in the setupext.py file of matplotlib during a version comparison. Specifically, a TypeError was raised because the comparison operation < was attempted between instances of str and int. This error caused the subprocess to exit with an error, leading to the failure of the build process.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1213: Installing backend dependencies: finished with status 'done' 1214: Preparing metadata (pyproject.toml): started 1215: Preparing metadata (pyproject.toml): finished with status 'done' 1216: Downloading matplotlib-1.4.3.tar.gz (50.4 MB) 1217: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 50.4/50.4 MB 139.8 MB/s eta 0:00:00 1218: Installing build dependencies: started 1219: Installing build dependencies: finished with status 'done' 1220: Getting requirements to build wheel: started 1221: Getting requirements to build wheel: finished with status 'error' 1222: error: subprocess-exited-with-error ... 1271: File "/tmp/pip-install-u6dzsuga/matplotlib_9ac056f8c1d8442d95c056b80bab4f92/setupext.py", line 445, in _check_for_pkg_config 1272: if (not is_min_version(version, min_version)): 1273: File "/tmp/pip-install-u6dzsuga/matplotlib_9ac056f8c1d8442d95c056b80bab4f92/setupext.py", line 173, in is_min_version 1274: return found_version >= expected_version 1275: File "/tmp/pip-build-env-5p5qmom7/overlay/lib/python3.10/site-packages/setuptools/_distutils/version.py", line 90, in __ge__ 1276: c = self._cmp(other) 1277: File "/tmp/pip-build-env-5p5qmom7/overlay/lib/python3.10/site-packages/setuptools/_distutils/version.py", line 343, in _cmp 1278: if self.version < other.version: 1279: TypeError: '<' not supported between instances of 'str' and 'int' 1280: [end of output] 1281: note: This error originates from a subprocess, and is likely not a problem with pip. 1282: error: subprocess-exited-with-error 1283: × Getting requirements to build wheel did not run successfully. 1284: │ exit code: 1 1285: ╰─> See above for output. 1286: note: This error originates from a subprocess, and is likely not a problem with pip. 1287: make: *** [Makefile:30: venv/.testenv] Error 1 1288: ##[error]Process completed with exit code 2.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.