Skip to content
Run Tests and Publish PyPI

Tickets/opsim 1197 (#113) #512

Sign in to view logs

Tickets/opsim 1197 (#113)

Tickets/opsim 1197 (#113) #512

Triggered via push October 3, 2024 22:20
@rhiannonlynnerhiannonlynne
pushed ec4a823
v3.0.0rc
Status Success
Total duration 33m 57s
Artifacts –

test_and_build.yaml

on: push
Matrix: tests
Build and Publish to PyPI
2m 58s
Build and Publish to PyPI
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Run Unit Tests (3.11, macos-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: codecov/codecov-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run Unit Tests (3.11, macos-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run Unit Tests (3.11, ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: codecov/codecov-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run Unit Tests (3.11, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v2. 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 to PyPI
The following actions use a deprecated Node.js version 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
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):