Update google/oss-fuzz digest to d872252

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
google/oss-fuzz (changelog)	action	digest	c11174f → d872252

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • On day 3 of the month (* * 3 * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[radarhere]

I'm surprised that the 7 day minimum release age didn't stop this from being created.

I guess it creates it anyway but leaves a 'pending check'.

[hugovk]

Looks like we also need prCreation="not-pending":

If you use minimumReleaseAge=3 days, prCreation="not-pending" and internalChecksFilter="strict" then Renovate only creates branches when 3 (or more days) have passed since the version was released.

https://docs.renovatebot.com/configuration-options/#suppress-branchpr-creation-for-x-days

internalChecksFilter="strict" is already the default, but prCreation="immediate" is the other default:

https://docs.renovatebot.com/configuration-options/#prcreation

I think the other PRs we merged just so happened to be over 7 days old anyway, when the "3rd of the month" schedule triggered.

---

Although this table says digest updates are "Generally not supported. Depends on the Manager, Datasource, and package(s)".

https://docs.renovatebot.com/key-concepts/minimum-release-age/#which-update-types-take-minimumreleaseage-into-account

Then again, we do have this check:

renovate/stability-daysWaiting for status to be reported — Updates have not met minimum release age requirement

---

Let's add the extra config and see what happens here.

[hugovk]

#9616 merged, and I checked "[x] If you want to rebase/retry this PR, check this box"

[hugovk]

Didn't mean to close it, the UI jumped as the force-push happened at the same time, meaning my click hit the close button instead of elsewhere!

[hugovk]

Maybe it's too late now this has already been created. Let's just merge this one and see what happens next time?