Skip to content

fix: rename stakingLimit field properly #501

fix: rename stakingLimit field properly

fix: rename stakingLimit field properly #501

Triggered via push October 15, 2024 07:28
Status Success
Total duration 2m 1s
Artifacts

checks.yml

on: push
security  /  Check security issues
1m 51s
security / Check security issues
docker  /  Check docker issues
6s
docker / Check docker issues
actions  /  Check GitHub Actions issues
8s
actions / Check GitHub Actions issues
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
docker / Check docker issues
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
actions / Check GitHub Actions issues
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
security / Check security issues
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
security / Check security issues
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, github/codeql-action/init@v2, github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/