The GitHub Actions run to deploy PR #20 produced 2 warnings about deprecations related to the JamesIves/github-pages-deploy-action used in the deploy job:
Deploy HTML documentation to publishing source
The following actions uses node12 which is deprecated and will be forced to run on node16: JamesIves/github-pages-deploy-action@v4.3.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy HTML documentation to publishing source
The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
One approach to resolve this issue is to increment the version of the action used: v4.4.1 of the action appears to upgrade to Node 16. It is possible the other warning has been resolved in more recent releases.
Alternatively, the action could be dropped from the workflow and replaced with workflow steps that perform the deployment without needing to push to a publishing source branch, as described here: https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#publishing-with-a-custom-github-actions-workflow.
The GitHub Actions run to deploy PR #20 produced 2 warnings about deprecations related to the
JamesIves/github-pages-deploy-actionused in thedeployjob:Deploy HTML documentation to publishing source
The following actions uses node12 which is deprecated and will be forced to run on node16: JamesIves/github-pages-deploy-action@v4.3.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy HTML documentation to publishing source
The
set-outputcommand is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/One approach to resolve this issue is to increment the version of the action used: v4.4.1 of the action appears to upgrade to Node 16. It is possible the other warning has been resolved in more recent releases.
Alternatively, the action could be dropped from the workflow and replaced with workflow steps that perform the deployment without needing to push to a publishing source branch, as described here: https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#publishing-with-a-custom-github-actions-workflow.