Skip to content

chore: Autogenerating code and RC Release preparation (#1092) #892

chore: Autogenerating code and RC Release preparation (#1092)

chore: Autogenerating code and RC Release preparation (#1092) #892

Triggered via push October 4, 2024 12:46
Status Success
Total duration 3m 0s
Artifacts
Matrix: Test
Slack notify on failure
0s
Slack notify on failure
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Test (3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/login-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/
Test (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/login-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/
Test (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/login-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/
Test (3.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/login-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/
Deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, sendgrid/dx-automator/actions/release@main, sendgrid/dx-automator/actions/datadog-release-metric@main. 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):