Skip to content

Fix job materialization when destination table does not yet exist #21

Fix job materialization when destination table does not yet exist

Fix job materialization when destination table does not yet exist #21

Triggered via pull request April 12, 2024 00:10
Status Success
Total duration 15m 1s
Artifacts

test.yml

on: pull_request
Matrix: Build
Matrix: Test
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Build (ubuntu-latest, 1.21.5)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v4, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build (macos-latest, 1.21.5)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v4, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Test (ubuntu-latest, 1.21.5)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v2, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Test (ubuntu-latest, 1.21.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test (macos-latest, 1.21.5)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v2, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Test (macos-latest, 1.21.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/