Skip to content

create-release

create-release #6

Manually triggered October 27, 2023 22:44
Status Failure
Total duration 44s
Artifacts

create-release.yaml

on: workflow_dispatch
create-release
35s
create-release
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
create-release
/home/runner/work/ui/ui/./.github/actions/semantic-package-json-update/action.yaml (Line: 10, Col: 7): Required property is missing: shell
create-release
/home/runner/work/ui/ui/./.github/actions/semantic-package-json-update/action.yaml (Line: 14, Col: 7): Required property is missing: shell
create-release
GitHub.DistributedTask.ObjectTemplating.TemplateValidationException: The template is not valid. /home/runner/work/ui/ui/./.github/actions/semantic-package-json-update/action.yaml (Line: 10, Col: 7): Required property is missing: shell,/home/runner/work/ui/ui/./.github/actions/semantic-package-json-update/action.yaml (Line: 14, Col: 7): Required property is missing: shell at GitHub.DistributedTask.ObjectTemplating.TemplateValidationErrors.Check() at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
create-release
Fail to load /home/runner/work/ui/ui/./.github/actions/semantic-package-json-update/action.yaml
create-release
Unexpected input(s) 'token', valid inputs are ['commit_message', 'branch', 'commit_options', 'add_options', 'status_options', 'file_pattern', 'repository', 'commit_user_name', 'commit_user_email', 'commit_author', 'tagging_message', 'push_options', 'skip_dirty_check', 'skip_fetch', 'skip_checkout', 'disable_globbing', 'create_branch', 'internal_git_binary']
create-release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/github-script@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/