Skip to content
Tag repo; build and publish assets

Merge pull request #1035 from opensafely-core/evansd/docker-compose-fix #542

Sign in to view logs

Merge pull request #1035 from opensafely-core/evansd/docker-compose-fix

Merge pull request #1035 from opensafely-core/evansd/docker-compose-fix #542

Triggered via push August 2, 2024 14:56
@evansdevansd
pushed 51c9e7e
main
Status Success
Total duration 1m 54s
Artifacts –

build_and_publish.yaml

on: push
tag-new-version
6s
tag-new-version
Build and publish PyPI package
40s
Build and publish PyPI package
Build and publish docker image
1m 28s
Build and publish docker image
Fit to window
Zoom out
Zoom in

Annotations

3 warnings and 1 notice
tag-new-version
The following actions uses Node.js version which is deprecated and will be forced to run on node20: mathieudutour/github-tag-action@fcfbdceb3093f6d85a3b194740f8c6cec632f4e2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and publish PyPI package
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Build and publish PyPI package
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/