Skip to content

Breaking change in patch version #430

@Donnerbart

Description

@Donnerbart

Hey folks,

You just released v1.0.17, I assume partially to fix the broken Maven Central release (v1.0.15 and v1.0.16 were never released).

But the fix also bumped the Java version from 8 to 17: de70958

Was this intentional? We still have to support Java 11 in our application, and this kind of breaking change was unexpected in a patch update.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions