You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Hi,
thank you for this good practices you'va gathered.
While reading https://keepachangelog.com/en/1.1.0/#bad-practices, in
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?
Regards
The text was updated successfully, but these errors were encountered: