Release v1.5.37 - Add ratenschutzDetailsBase64 field and deprecate legacy rate protection fields

[github-actions]

Summary

This release adds support for Base64-encoded rate protection data in the Kundenangaben API, enabling seamless integration with external rate protection microfrontends.

New Field

ratenschutzDetailsBase64 - A new optional field in the Ratenschutz (rate protection) model:

• Type: String (Base64-encoded)
• Format: Base64 string containing rate protection details from external microfrontends
• Max Size: 100 KB
• Validation: Base64 format validation

API Changes

Available in all operations:

• GET /kundenangaben/{vorgangsnummer} - Retrieve rate protection data
• POST /kundenangaben - Import rate protection data
• PUT /kundenangaben/{vorgangsnummer} - Update rate protection data

Deprecated Fields

The following fields in Ratenschutz are now deprecated in favor of ratenschutzDetailsBase64:

• versicherungsbeginn
• versicherungsdauerInJahren
• praemienzahlung
• risikoabsicherungswuensche

Note: The fields id and kundenreferenzIdDerVersichertenPerson remain active for object identification and referencing.

Migration Path

• Existing integrations continue to work without changes
• Legacy data with deprecated fields will still be returned in GET responses
• New integrations should use ratenschutzDetailsBase64 exclusively
• Input values for deprecated fields in POST/PUT operations will be ignored

Backward Compatibility

✅ Fully backward compatible - no API version change required
✅ All deprecated fields remain readable
✅ New field is optional (nullable)