Skip to content

chore: Updating Python Requirements (#316) #356

chore: Updating Python Requirements (#316)

chore: Updating Python Requirements (#316) #356

Triggered via push April 26, 2024 17:12
Status Success
Total duration 1m 41s
Artifacts

ci.yml

on: push
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

8 warnings and 9 notices
tests (3.8, django42)
Starting action
tests (3.8, django42)
HTTP Request: GET https://api.github.com/repos/edx/portal-designer "HTTP/1.1 200 OK"
tests (3.8, django42)
Computing coverage files & badge
tests (3.8, django42)
HTTP Request: GET https://img.shields.io/static/v1?label=Coverage&message=86%25&color=orange "HTTP/1.1 200 OK"
tests (3.8, django42)
Generating HTML coverage report
tests (3.8, django42)
Saving coverage files
tests (3.8, django42)
Files saved
tests (3.8, django42)
You can browse the full coverage report at: https://htmlpreview.github.io/?https://github.com/edx/portal-designer/blob/python-coverage-comment-action-data/htmlcov/index.html You can use the following URLs to display your badge: - Badge SVG available at: https://raw.githubusercontent.com/edx/portal-designer/python-coverage-comment-action-data/badge.svg - Badge from shields endpoint is easier to customize but doesn't work with private repo: https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/edx/portal-designer/python-coverage-comment-action-data/endpoint.json - Badge from shields dynamic url (less useful but you never know): https://img.shields.io/badge/dynamic/json?color=brightgreen&label=coverage&query=%24.message&url=https%3A%2F%2Fraw.githubusercontent.com%2Fedx%2Fportal-designer%2Fpython-coverage-comment-action-data%2Fendpoint.json See more details and ready-to-copy-paste-markdown at: https://github.com/edx/portal-designer/tree/python-coverage-comment-action-data
tests (3.8, django42)
Ending action
tests (3.8, pii_check)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-python@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
tests (3.8, pii_check)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
tests (3.8, check_keywords)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-python@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
tests (3.8, check_keywords)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
tests (3.8, quality)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-python@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
tests (3.8, quality)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
tests (3.8, django42)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-python@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
tests (3.8, django42)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/