Skip to content

chore(deps): bump cryptography from 41.0.7 to 42.0.4 #338

chore(deps): bump cryptography from 41.0.7 to 42.0.4

chore(deps): bump cryptography from 41.0.7 to 42.0.4 #338

Triggered via push May 3, 2024 14:07
Status Failure
Total duration 1m 3s
Artifacts 1

publish.yml

on: push
🏗️ build package
12s
🏗️ build package
📦 publish to TestPyPI
31s
📦 publish to TestPyPI
📦 publish to PyPI
0s
📦 publish to PyPI
☀️ create release
0s
☀️ create release
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
🏗️ build package
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
🏗️ build package
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
📦 publish to TestPyPI
Input 'password' has been deprecated with message: UNSUPPORTED GITHUB ACTION VERSION You are using `pypa/gh-action-pypi-publish@master`. The `master` branch of this project has been sunset and will not receive any updates, not even security bug fixes. Please, make sure to use a supported version. If you want to pin to v1 major version, use `pypa/gh-action-pypi-publish@release/v1`. If you feel adventurous, you may opt to use use `pypa/gh-action-pypi-publish@unstable/v1` instead. A more general recommendation is to pin to exact tags or commit SHAs. Please also consider migrating your setup to use secretless publishing: https://github.com/marketplace/actions/pypi-publish#trusted-publishing https://stand-with-ukraine.pp.ua
📦 publish to TestPyPI
Input 'repository_url' has been deprecated with message: UNSUPPORTED GITHUB ACTION VERSION You are using `pypa/gh-action-pypi-publish@master`. The `master` branch of this project has been sunset and will not receive any updates, not even security bug fixes. Please, make sure to use a supported version. If you want to pin to v1 major version, use `pypa/gh-action-pypi-publish@release/v1`. If you feel adventurous, you may opt to use use `pypa/gh-action-pypi-publish@unstable/v1` instead. A more general recommendation is to pin to exact tags or commit SHAs. Please also consider migrating your setup to use secretless publishing: https://github.com/marketplace/actions/pypi-publish#trusted-publishing https://stand-with-ukraine.pp.ua
📦 publish to TestPyPI: # >> PyPA publish to PyPI GHA: UNSUPPORTED GITHUB ACTION VERSION <<#L1
You are using "pypa/gh-action-pypi-publish@master". The "master" branch of this project has been sunset and will not receive any updates, not even security bug fixes. Please, make sure to use a supported version. If you want to pin to v1 major version, use "pypa/gh-action-pypi-publish@release/v1". If you feel adventurous, you may opt to use use "pypa/gh-action-pypi-publish@unstable/v1" instead. A more general recommendation is to pin to exact tags or commit shas.
📦 publish to TestPyPI: # >> PyPA publish to PyPI GHA: POTENTIALLY INVALID TOKEN <<#L1
It looks like you are trying to use an API token to authenticate in the package index and your token value does not start with "pypi-" as it typically should. This may cause an authentication error. Please verify that you have copied your token properly if such an error occurs.

Artifacts

Produced during runtime
Name Size
buildfiles Expired
295 KB