release: Releasing version 1.0.4 

fix: handle non-standard field casing in MapContains queries Modified processMapContainsQuery to support Map fields with uppercase/non-standard casing (e.g., 'Positions' instead of 'positions'). The method now tries both the standard lowercase naming convention and the original field name when resolving Map fields. This fixes repository methods like findByPositionsMapContainsCusip when the Java field uses non-standard casing to match JSON data from external sources like RIOT exports.

release: Releasing version 1.0.2 

release: Releasing version 1.0.1 

release: Releasing version 1.0.0 

release: Releasing version 1.0.0-RC4 

release: Releasing version 1.0.0-RC3 

Releasing version 1.0.0-RC2 

Releasing version 1.0.0-RC1 

Releasing version 1.0.0-RC2