fix: use correct main module name in templates #1069
- ci requires an approval to start deploying changes
the-forest-tree- ci requires an approval to start deploying changes
hrflow_connectors.yml
on: push
core-tests
2m 58s
connectors-integration-tests
ci
waiting for review
post-release
4s
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
| Event | Environments |
|---|---|
the-forest-tree
requested review
|
ci |
|
the-forest-tree
approved
|
release |
|
the-forest-tree
approved
|
release |
|
the-forest-tree
approved
|
ci |
Annotations
9 warnings
|
core-tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2, actions/cache@v2, excitedleigh/setup-nox@v2.0.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
core-tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v2, actions/cache@v2, excitedleigh/setup-nox@v2.0.0, aws-actions/configure-aws-credentials@v2, aws-actions/aws-secretsmanager-get-secrets@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
cd
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
cd
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v2, actions/cache@v2. 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):
|
|
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):
|
|
post-release
The following actions use a deprecated Node.js version and will be forced to run on node20: peter-evans/repository-dispatch@v2.1.2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|