test postgres and duckdb

rest_api paginator: Allows using json_response in place of json_link #960

Sign in to view logs

Triggered via pull request July 24, 2024 11:28

synchronize #533

fix/json_response-key-in-paginator-config

Status Success

Total duration 1m 59s

Artifacts –

test_on_local_destinations.yml

on: pull_request

get_changed_sources / get_changed_sources

Matrix: test destinations postgres and duckdb

Annotations

5 warnings

get_changed_sources / get_changed_sources

The following actions uses Node.js version which is deprecated 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/

test destinations postgres and duckdb (macos-latest)

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@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 destinations postgres and duckdb (macos-latest)

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

test destinations postgres and duckdb (windows-latest)

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@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 destinations postgres and duckdb (windows-latest)

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/