Skip to content

Explain the reason for support parsing legacy restricted types #1706

Explain the reason for support parsing legacy restricted types

Explain the reason for support parsing legacy restricted types #1706

Triggered via pull request October 16, 2024 21:11
Status Success
Total duration 4m 58s
Artifacts 2

compatibility-check.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
mainnet / check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
testnet / check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "mainnet-checking-results", "testnet-checking-results". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
mainnet-checking-results
17.4 MB
testnet-checking-results
187 MB