Fix misleading AI activity messages that could be mistaken for actual database operations. #4571
Triggered via pull request
March 16, 2026 07:20
akshay-joshi
Status
Success
Total duration
1h 29m 48s
Artifacts
10
run-feature-tests-pg.yml
on: pull_request
Matrix: run-feature-tests-pg
Annotations
5 warnings
|
run-feature-tests-pg (18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-feature-tests-pg (15)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-feature-tests-pg (16)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-feature-tests-pg (14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-feature-tests-pg (17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
regression-log-pg14
|
2.86 KB |
sha256:d9bc8e96a6007758eb8feddb6566b35e9877bf59341f7c826165295437e82264
|
|
|
regression-log-pg15
|
2.86 KB |
sha256:2e84faeb33ec89c551e7dcc97131f3f888a1517b3d9c22b768eca7a8b1010717
|
|
|
regression-log-pg16
|
2.85 KB |
sha256:de32eaa92d4b56d61e59db812aef1d7c2256ddf1295a3148ed529e2f742d1ced
|
|
|
regression-log-pg17
|
2.84 KB |
sha256:cde519b97bdd82a0fa72b16a743dcd083c645f2447503c513194f39e0b997b5b
|
|
|
regression-log-pg18
|
2.83 KB |
sha256:3a9614d4c68fd83c1fe3b5036dc3762c42dba98d733cd36bb082847a795a5f05
|
|
|
server-log-pg14
|
111 KB |
sha256:e60f3cb2f88d34f4972ed16689d9c42df570fe6c936e3ace579ec62d59b74223
|
|
|
server-log-pg15
|
111 KB |
sha256:5f383f4070d8016ff02d6d558e08114b59f61615500408eead6e5ae3a9d31c6b
|
|
|
server-log-pg16
|
111 KB |
sha256:337d6ce5162332268321c8bc4ce311d9655160607f28a3f029a5fcfd683cf8fd
|
|
|
server-log-pg17
|
112 KB |
sha256:d6ab3c2eb923ba5085675b40a12ff87be39d2f972b1224fd4f7ffd0b25cf43fb
|
|
|
server-log-pg18
|
112 KB |
sha256:467298935d78dfb193be6eeae366b5d48d21e94a9af4ccd862d9ead43cb646f0
|
|