Skip to content

move deprecation notice under heading to get it picked up by npm (?) #7

move deprecation notice under heading to get it picked up by npm (?)

move deprecation notice under heading to get it picked up by npm (?) #7

Triggered via push July 2, 2024 12:55
Status Failure
Total duration 1m 28s
Artifacts 1

gh-pages.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
pages
Creating Pages deployment failed
pages
HttpError: Invalid deployment branch and no branch protection rules set in the environment. Deployments are only allowed from gh-pages at /home/runner/work/_actions/actions/deploy-pages/v2/node_modules/@octokit/request/dist-node/index.js:86:1 at processTicksAndRejections (node:internal/process/task_queues:96:5) at createPagesDeployment (/home/runner/work/_actions/actions/deploy-pages/v2/src/internal/api-client.js:126:1) at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v2/src/internal/deployment.js:80:1) at main (/home/runner/work/_actions/actions/deploy-pages/v2/src/index.js:30:1)
pages
Error: Failed to create deployment (status: 400) with build version c9185670f68654c190f488e7ea412131bf9cf8fe. Responded with: Invalid deployment branch and no branch protection rules set in the environment. Deployments are only allowed from gh-pages
pages
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/upload-artifact@v3, actions/deploy-pages@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "github-pages". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
github-pages Expired
13.8 MB