Skip to content

Merge pull request #132 from codacy/add-custom-registry #11

Merge pull request #132 from codacy/add-custom-registry

Merge pull request #132 from codacy/add-custom-registry #11

Triggered via push July 11, 2024 14:11
Status Success
Total duration 16s
Artifacts
Release GitHub Actions
7s
Release GitHub Actions
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
Release GitHub Actions
The following actions uses node12 which is deprecated and will be forced to run on node16: technote-space/release-github-actions@v4. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Release GitHub Actions
The following actions uses Node.js version which is deprecated and will be forced to run on node20: technote-space/release-github-actions@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Release GitHub Actions
>> hint: Using 'master' as the name for the initial branch. This default branch name
Release GitHub Actions
>> hint: is subject to change. To configure the initial branch name to use in all
Release GitHub Actions
>> hint: of your new repositories, which will suppress this warning, call:
Release GitHub Actions
>> hint:
Release GitHub Actions
>> hint: git config --global init.defaultBranch <name>
Release GitHub Actions
>> hint:
Release GitHub Actions
>> hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
Release GitHub Actions
>> hint: 'development'. The just-created branch can be renamed via this command:
Release GitHub Actions
>> hint:
Release GitHub Actions
>> hint: git branch -m <name>