Skip to content

[TCE-1154] Inconsistencies in --registryAddress handling #36

[TCE-1154] Inconsistencies in --registryAddress handling

[TCE-1154] Inconsistencies in --registryAddress handling #36

Triggered via issue October 30, 2024 20:58
Status Success
Total duration 17s
Artifacts

create_issue.yml

on: issues
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
jira
The following actions uses node12 which is deprecated and will be forced to run on node16: atlassian/[email protected], atlassian/[email protected], actions/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
jira
The following actions use a deprecated Node.js version and will be forced to run on node20: atlassian/[email protected], atlassian/[email protected], actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
jira
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
jira
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
jira
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/