Skip to content

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

rest_api paginator: Allows using json_response in place of json_link

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

Triggered via pull request July 24, 2024 11:28
@willi-muellerwilli-mueller
synchronize #533
Status Success
Total duration 1m 49s
Artifacts

test_on_local_destinations_forks.yml

on: pull_request_target
authorize
0s
authorize
get_changed_sources  /  get_changed_sources
5s
get_changed_sources / get_changed_sources
FORKS - test on local postgres and duckdb
1m 17s
FORKS - test on local postgres and duckdb
Fit to window
Zoom out
Zoom in

Annotations

3 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/
FORKS - test on local postgres and duckdb
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/
FORKS - test on local postgres and duckdb
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/