Skip to content
SubQL Deploy

fix: asset metadata updates (#248) #230

Sign in to view logs

fix: asset metadata updates (#248)

fix: asset metadata updates (#248) #230

Triggered via push August 29, 2024 08:50
@filo87filo87
pushed d310b6a
main
Status Success
Total duration 5d 2h 51m 5s
Artifacts –

deploy.yml

on: push
Matrix: Deploy to SubQL multichain (mainnet)
Matrix: Deploy to SubQL multichain (staging)
Matrix: Deploy to SubQL (staging)
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
@hieronx
hieronx
approved Sep 3, 2024
pools-multichain

Annotations

3 warnings
Deploy to SubQL (staging) (development) / subql_deploy_workflow
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/
Deploy to SubQL multichain (staging) (demo) / subql_deploy_workflow
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/
Deploy to SubQL multichain (mainnet) (centrifuge) / subql_deploy_workflow
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/