Skip to content

Bump github.com/jackc/pgx/v5 from 5.7.1 to 5.9.0 in /test #829

Bump github.com/jackc/pgx/v5 from 5.7.1 to 5.9.0 in /test

Bump github.com/jackc/pgx/v5 from 5.7.1 to 5.9.0 in /test #829

Triggered via pull request April 16, 2026 22:41
Status Success
Total duration 6m 5s
Artifacts

pr-check.yaml

on: pull_request
prepr-check  /  prepr-check
5m 56s
prepr-check / prepr-check
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
prepr-check / prepr-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-go@6edd4406fa81c3da01a34fa6f6343087c207a568, github/codeql-action/analyze@1b1aada464948af03b950897e5eb522f92603cc2, github/codeql-action/init@1b1aada464948af03b950897e5eb522f92603cc2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
prepr-check / prepr-check
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
prepr-check / prepr-check
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.16.5.
prepr-check / prepr-check
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration