[scala-steward]

About this PR

📦 Updates org.postgresql:postgresql from 42.7.13 to 42.7.14

📜 Changelog

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.postgresql", artifactId = "postgresql" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.postgresql", artifactId = "postgresql" }
}]

^{labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1}

[mergify]

Queued — the merge queue status continues in this comment ↓.

[mergify]

queue

⚠️ Configuration not compatible with a branch protection setting

Details

The branch protection of main requires branches to be up to date before merging. The merge queue tests pull requests in a draft PR built on the latest base branch, then merges the original pull requests. Their own branches were not updated with that base branch, so GitHub considers them out of date and refuses to merge them.

To fix it, turn off Require branches to be up to date before merging in the branch protection of main. It is safe to turn off: the merge queue already tests every pull request it merges on the latest base branch, together with the ones queued ahead of it. That is what this setting checks. Changing the setting needs admin access.

If you need to keep the setting:

• Use merge_method: fast-forward: the queue pushes the tested draft PR's branch to the base branch itself, which the setting does not refuse.
• Use in-place checks: Mergify tests each pull request on its own branch, one at a time, which gives up parallel checks and batches. To do so, set merge_queue.max_parallel_checks: 1 and merge_queue.mode: serial, set every queue rule batch_size: 1 and max_checks_retries: 0, and avoid two-step CI (make merge_conditions identical to queue_conditions).

Learn more in the documentation.

[mergify]

⏳ Waiting for queue conditions

Queue rule default · 1 of 5 left

• any of · required by GitHub branch protection:
  • check-neutral = Build And Test
  • check-skipped = Build And Test
  • check-success = Build And Test

Queue rule default: 4 met

• -closed
• -conflict
• -draft
• any of:
  • -mergify-configuration-changed
  • check-success = @mergify/Configuration changed
  • check-success = @mergify/Configuration has been deleted

_{Times in UTC · dashboard · how the merge queue works}

[mergify]

queue

⚠️ Configuration not compatible with a branch protection setting

Details

The branch protection of main requires branches to be up to date before merging. The merge queue tests pull requests in a draft PR built on the latest base branch, then merges the original pull requests. Their own branches were not updated with that base branch, so GitHub considers them out of date and refuses to merge them.

To fix it, turn off Require branches to be up to date before merging in the branch protection of main. It is safe to turn off: the merge queue already tests every pull request it merges on the latest base branch, together with the ones queued ahead of it. That is what this setting checks. Changing the setting needs admin access.

If you need to keep the setting:

• Use merge_method: fast-forward: the queue pushes the tested draft PR's branch to the base branch itself, which the setting does not refuse.
• Use in-place checks: Mergify tests each pull request on its own branch, one at a time, which gives up parallel checks and batches. To do so, set merge_queue.max_parallel_checks: 1 and merge_queue.mode: serial, set every queue rule batch_size: 1 and max_checks_retries: 0, and avoid two-step CI (make merge_conditions identical to queue_conditions).

Learn more in the documentation.