Skip to content

chore: Add semantic release config (#199) #1

chore: Add semantic release config (#199)

chore: Add semantic release config (#199) #1

Triggered via push October 31, 2024 03:08
Status Failure
Total duration 2m 13s
Artifacts

release.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Release
AggregateError: EnvVarError: Environment variable not found: HACKAGE_TOKEN. Check the README.md for config info. at verifyConditions (/home/runner/work/_actions/cycjimmy/semantic-release-action/v4/node_modules/semantic-release-hackage/dist/verifyConditions.js:9:15) at validator (file:///home/runner/work/_actions/cycjimmy/semantic-release-action/v4/node_modules/semantic-release/lib/plugins/normalize.js:36:30) at file:///home/runner/work/_actions/cycjimmy/semantic-release-action/v4/node_modules/semantic-release/lib/plugins/pipeline.js:38:42 at next (file:///home/runner/work/_actions/cycjimmy/semantic-release-action/v4/node_modules/semantic-release/node_modules/p-reduce/index.js:16:10)
Release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/