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

Can changelogs be bad? / Ignoring Deprecations #649

Open
PhilLAL opened this issue Jan 31, 2025 · 0 comments
Open

Can changelogs be bad? / Ignoring Deprecations #649

PhilLAL opened this issue Jan 31, 2025 · 0 comments

Comments

@PhilLAL
Copy link

PhilLAL commented Jan 31, 2025

Hi,
thank you for this good practices you'va gathered.

While reading https://keepachangelog.com/en/1.1.0/#bad-practices, in

When people upgrade from one version to another, it should be painfully clear when something will break. It should be possible to upgrade to a version that lists deprecations, remove what's deprecated, then upgrade to the version where the deprecations become removals.

If you do nothing else, list deprecations, removals, and any breaking changes in your changelog.

I do not understand what means It should be possible to upgrade to a version that lists deprecations, remove what's deprecated, then upgrade to the version where the deprecations become removals.

Does it mean the following?

It should be possible to consecutively upgrade to a version giving a list of deprecations, then remove what's deprecated, and then upgrade to the version where the deprecations become removals.

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