← Back to events
ActiveTechRelease8.0.0-rc.14

v8.0.0-rc.14-dev.16: Fix nullable Mongo list container validation (#30568)

What happened

Linked issue Follow-up to #30051 , found during fresh consumer QA. No Linear ticket, per the original project direction. At a glance optionalStrings String[]? optionalNullableStrings String?[]? Both fields now admit an explicit null container in Mongo; only the second admits null elements. Previously, omission worked but an explicit null container failed database validation. Summary Make Mongo collection validation…

Summary assembled by rule from the sources below

Why it's spreading

Sources