Fix using rails-ex repo and rails-postgresql-persistent.json file #10786
auto-merge-on-demand.yml
on: issue_comment
gather-pull-requests
3s
Matrix: validate-pr
Annotations
11 errors and 11 warnings
|
Validation of Pull Request #638
### Pull Request validation
#### Failed
🔴 Review - Missing review from a member (_**1** required_)
#### Success
🟢 CI - All checks have passed
|
|
Validation of Pull Request #644
### Pull Request validation
#### Failed
🔴 Review - Missing review from a member (_**1** required_)
#### Success
🟢 CI - All checks have passed
|
|
Validation of Pull Request #639
### Pull Request validation
#### Failed
🔴 Review - Missing review from a member (_**1** required_)
#### Success
🟢 CI - All checks have passed
|
|
Validation of Pull Request #640
### Pull Request validation
#### Failed
🔴 Review - Missing review from a member (_**1** required_)
#### Success
🟢 CI - All checks have passed
|
|
Validation of Pull Request #630
### Pull Request validation
#### Failed
🔴 Review - Missing review from a member (_**1** required_)
#### Success
🟢 CI - All checks have passed
|
|
Validation of Pull Request #637
### Pull Request validation
#### Failed
🔴 Review - Missing review from a member (_**1** required_)
#### Success
🟢 CI - All checks have passed
|
|
Validation of Pull Request #642
### Pull Request validation
#### Failed
🔴 Review - Missing review from a member (_**1** required_)
#### Success
🟢 CI - All checks have passed
|
|
Validation of Pull Request #604
### Pull Request validation
#### Failed
🔴 Review - Missing review from a member (_**1** required_)
#### Success
🟢 CI - All checks have passed
|
|
Validation of Pull Request #631
### Pull Request validation
#### Failed
🔴 Review - Missing review from a member (_**1** required_)
#### Success
🟢 CI - All checks have passed
|
|
Validation of Pull Request #641
### Pull Request validation
#### Failed
🔴 Review - Missing review from a member (_**1** required_)
#### Success
🟢 CI - All checks have passed
|
|
Validation of Pull Request #601
### Pull Request validation
#### Failed
🔴 Review - Missing review from a member (_**1** required_)
#### Success
🟢 CI - All checks have passed
|
|
Validation of Pull Request #638
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/issue-commentator@v1, redhat-plumbers-in-action/pull-request-validator@v2. 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/
|
|
Validation of Pull Request #644
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/issue-commentator@v1, redhat-plumbers-in-action/pull-request-validator@v2. 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/
|
|
Validation of Pull Request #639
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/issue-commentator@v1, redhat-plumbers-in-action/pull-request-validator@v2. 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/
|
|
Validation of Pull Request #640
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/issue-commentator@v1, redhat-plumbers-in-action/pull-request-validator@v2. 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/
|
|
Validation of Pull Request #630
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/issue-commentator@v1, redhat-plumbers-in-action/pull-request-validator@v2. 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/
|
|
Validation of Pull Request #637
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/issue-commentator@v1, redhat-plumbers-in-action/pull-request-validator@v2. 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/
|
|
Validation of Pull Request #642
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/issue-commentator@v1, redhat-plumbers-in-action/pull-request-validator@v2. 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/
|
|
Validation of Pull Request #604
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/issue-commentator@v1, redhat-plumbers-in-action/pull-request-validator@v2. 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/
|
|
Validation of Pull Request #631
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/issue-commentator@v1, redhat-plumbers-in-action/pull-request-validator@v2. 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/
|
|
Validation of Pull Request #641
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/issue-commentator@v1, redhat-plumbers-in-action/pull-request-validator@v2. 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/
|
|
Validation of Pull Request #601
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/issue-commentator@v1, redhat-plumbers-in-action/pull-request-validator@v2. 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/
|