Skip to content

feat: add check to verify backend connection in readiness probe #3207

feat: add check to verify backend connection in readiness probe

feat: add check to verify backend connection in readiness probe #3207

Triggered via pull request April 10, 2026 23:24
@nancynhnancynh
synchronize #919
backend-check
Status Success
Total duration 56s
Artifacts

govulncheck.yaml

on: pull_request
Run govulncheck
54s
Run govulncheck
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Run govulncheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. 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/
Run govulncheck
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0y4bZaQAAAAA1DofW5q0FT5/diw37Ed5LTVNQMzExMDAwMTA2MDUzAEVkZ2U=
Run govulncheck
Failed to restore: Cache service responded with 400