Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

versioning scheme and breaking changes #142

Open
jpfroud opened this issue Apr 16, 2021 · 0 comments
Open

versioning scheme and breaking changes #142

jpfroud opened this issue Apr 16, 2021 · 0 comments

Comments

@jpfroud
Copy link

jpfroud commented Apr 16, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant