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

feat: add deprecation notice #109

Merged
merged 1 commit into from
Aug 15, 2024
Merged

feat: add deprecation notice #109

merged 1 commit into from
Aug 15, 2024

Conversation

sgoudham
Copy link
Contributor

ref: https://semver.org/#how-should-i-handle-deprecating-functionality

Deprecating existing functionality is a normal part of software development and is often required to make forward progress. When you deprecate part of your public API, you should do two things: (1) update your documentation to let users know about the change, (2) issue a new minor release with the deprecation in place. Before you completely remove the functionality in a new major release there should be at least one minor release that contains the deprecation so that users can smoothly transition to the new API.

@sgoudham sgoudham merged commit d023fd5 into main Aug 15, 2024
6 checks passed
@sgoudham sgoudham deleted the fix/deprecation-notice branch August 15, 2024 00:26
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

Successfully merging this pull request may close these issues.

1 participant