Skip to content

versioning scheme and breaking changes #142

Open
@jpfroud

Description

@jpfroud

Hi,

Would be great if you could change the current versioning scheme to respect the most used semantic versionning:

Summary
Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards compatible manner, and
PATCH version when you make backwards compatible bug fixes.

It's a pain every time we update our dependencies, we have to remember that assertj has breaking changes even though only minor version were updated.

By the way, we're stuck on version 3.17 because of this change:

Breaking change: disable bare name getter by default, to get the previous behaviour back, call Assertions.setExtractBareNamePropertyMethods(true);

What's the simplest way to get the previous behaviour? Adding this line in every test?

Regards

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