2.6.0: Harness.handle_exec, Harness.add_relation improvements, and more #20
benhoytpublish.yml
on: release
Matrix: framework-tests / test-real-pebble
Matrix: framework-tests / test
Matrix: hello-charm-tests / hello-charm-tests
Matrix: observability-charm-tests / o11y-charm-tests
framework-tests
/
lint
45s
framework-tests
/
static
46s
framework-tests
/
pip-install
9s
Build and Publish to PyPI
47s
Annotations
13 warnings and 1 notice
|
framework-tests / pip-install
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
hello-charm-tests / hello-charm-tests (juju/hello-juju-charm)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
hello-charm-tests / hello-charm-tests (jnsgruk/hello-kubecon)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
framework-tests / lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
framework-tests / static
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
framework-tests / test-real-pebble (ubuntu-latest, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2, actions/setup-go@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
framework-tests / test-real-pebble (ubuntu-latest, 3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2, actions/setup-go@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
framework-tests / test (ubuntu-latest, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
framework-tests / test (ubuntu-latest, 3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
framework-tests / test (macos-latest, 3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
framework-tests / test (macos-latest, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Build and Publish to PyPI
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/
|
|
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 to PyPI
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|