Skip to content

add release to nuget and github (#723) #131

add release to nuget and github (#723)

add release to nuget and github (#723) #131

Triggered via push November 1, 2024 20:05
Status Failure
Total duration 2m 27s
Artifacts 1

publish-docs.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
deploy
Creating Pages deployment failed
deploy
HttpError: Invalid deployment branch and no branch protection rules set in the environment. Deployments are only allowed from gh-pages at D:\a\_actions\actions\deploy-pages\v4\node_modules\@octokit\request\dist-node\index.js:124:1 at processTicksAndRejections (node:internal/process/task_queues:95:5) at createPagesDeployment (D:\a\_actions\actions\deploy-pages\v4\src\internal\api-client.js:125:1) at Deployment.create (D:\a\_actions\actions\deploy-pages\v4\src\internal\deployment.js:74:1) at main (D:\a\_actions\actions\deploy-pages\v4\src\index.js:30:1)
deploy
Error: Failed to create deployment (status: 400) with build version f3ddb94bf9580cb8b1d18d106878c894dcc25387. Request ID 5039:189844:C7560C:18310A4:6725351C Responded with: Invalid deployment branch and no branch protection rules set in the environment. Deployments are only allowed from gh-pages
deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
github-pages Expired
601 KB