Skip to content

chore: add release note workflow #174

chore: add release note workflow

chore: add release note workflow #174

Triggered via push September 10, 2024 13:13
Status Failure
Total duration 1m 5s
Artifacts

release.yml

on: push
Changesets  /  Changesets
47s
Changesets / Changesets
Generate Release Notes
54s
Generate Release Notes
Matrix: Prerelease CI / CI: JavaScript
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Generate Release Notes
Validation Failed: {"resource":"Release","code":"custom","field":"pre_receive","message":"pre_receive Sorry, branch or tag names consisting of 40 hex characters are not allowed."}, {"resource":"Release","code":"custom","message":"Published releases must have a valid tag"}
Changesets / Changesets
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, wow-actions/use-app-token@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Generate Release Notes
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/create-release@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Generate Release Notes
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/create-release@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/