Dmytro Nosan

Thank you for your feedback, @wilkinsona. Feel free to reach out if any further work is required on this.

[6.5.0.RELEASE](https://github.com/redis/lettuce/releases/tag/6.5.0.RELEASE) has been released. I bumped the version to 6.5.0 and uncommented tests for `regex` and `subnet`.

Thanks, @philwebb. Should I revert bump version commit, meanwhile? I know that you have a separate workflow for dependencies upgrade. So maybe, this version bump shouldn’t be included here.

@mhalbritter I reviewed the issue page at https://github.com/spring-io/start.spring.io/issues/new/choose, and I noticed it includes a `Report of a security vulnerability` option, but the repository itself does not have a `SECURITY.md`. Is...

Thank you, @snicoll

The third [option](https://github.com/nosan/spring-boot/commit/35f366897b30ea945d61f06540eecf9c79861efe) is similar to the first approach, but instead of supporting only **.yaml** files, it also supports _multi-document_ **.properties**. ```java @SpringJUnitConfig @TestPropertySource(locations = { "classpath:test.yaml", "classpath:test1.yaml", "classpath:test.properties" },...

> Once thing that makes me pause is that we don't/can't support spring.config.activate.on-profile for multi-document files. I was trying to add this support, but to be honest, I have not...

Honestly, the more I think about this PR, the more I want to close it. This YAML support is so limited, and I’m not sure whether it’s worth including in...

https://github.com/spring-projects/spring-boot/compare/main...nosan:spring-boot:gh-42782 contains a potential fix.

> The message lookup for EL expressions like `${validatedValue}` and for Bean Validation attributes such as `{max}` could be skipped. For example:`size.person.name=${validatedValue} must be between {min} and {max}`. Currently, `MessageSourceMessageInterpolator`...