Skip to content

feat: 🎸 add assetId in GET /assets/{asset} response #1448

feat: 🎸 add assetId in GET /assets/{asset} response

feat: 🎸 add assetId in GET /assets/{asset} response #1448

Triggered via push November 1, 2024 19:14
Status Success
Total duration 3m 27s
Artifacts

main.yml

on: push
Building and releasing project
1m 12s
Building and releasing project
Check if fast forwarding is possible
0s
Check if fast forwarding is possible
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Building
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/
Linting
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/
Testing
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/
Building and releasing project
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/