Nullable types must be explicit

Exported MR into patch to use in composer.

keopx → changed the visibility of the branch 3500347-nullable-types-must-1.x to hidden.

@kiseleva.t,

You can use MRs in Composer as well. To do so, simply add ".patch" at the end of the MR URL.
Example:

"drupal/node_revision_delete": {
    "#3500347 - Nullable types must be explicit": "https://git.drupalcode.org/project/node_revision_delete/-/merge_requests/32.patch"
}

Note that I tested MR !31 on Drupal 11.2 and it works correctly.

Careful with the approach above, as the patch is associated to the MR so it will change over time. See https://architecture.lullabot.com/adr/20220429-composer-patch-files/

Thank you @pcambra for the clarification — it's true that I didn’t add a disclaimer about the approach I mentioned.
It should indeed be used with caution.
On my side, I’ve been using it for open MRs (even RTBC ones) for a long time without changes (but still not merged), while having tests run at every composer install (which can indeed break something if the MR has changed).
For greater peace of mind, it’s definitely better to use a local copy of the patch (which can be generated with the approach I mentioned).

Automatically closed - issue fixed for 2 weeks with no activity.

Hi there,

I hope you're doing well!

I'm wondering why this issue was marked as fixed and closed. Unless I'm mistaken, only MR !32 has been merged (into the 8.x-1.x branch), while MR !31 (targeting the 2.0.x branch) is still open.
Also, I couldn't find any new release that includes the fix — neither for 8.x-1.x nor for 2.0.x.

If the fix is confirmed and everything looks good, would it be possible to merge MR !31 and tag new releases accordingly?

Thanks a lot!