Skip to content

Simply removing JDBC generated key support is NOT a fix #1129

Simply removing JDBC generated key support is NOT a fix

Simply removing JDBC generated key support is NOT a fix #1129

Triggered via issue November 15, 2023 20:44
Status Success
Total duration 14s
Artifacts

build-native.yml

on: issue_comment
Check conditions
5s
Check conditions
Build matrix
0s
Build matrix
Matrix: Build native libraries
Push new native libraries to branch
0s
Push new native libraries to branch
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Check conditions
The following actions uses node12 which is deprecated and will be forced to run on node16: khan/pull-request-comment-trigger@v1.1.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check conditions
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Check conditions
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/