-
Notifications
You must be signed in to change notification settings - Fork 48
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
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin #1000
Comments
I don't think we plan any (significant) breaking changes. At best I might want to change some REST status codes (I think one or more of our 200 should be 202, but most are already correct). Will leave this open until we have a discussion on this. |
Closing this issue as there are no breaking changes. |
Reopening as apparently we are discussing changing return codes. |
Closing this as #1083 PR is merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin
As mentioned in this META Issue, we want to track and increase transparency around the breaking changes planned for the 3.0 release across participating plugins.
Please kindly document all planned breaking changes related to your plugin for 3.0 here, by sharing detailed information about the changes, expected impact, and any guidance for users or other teams to adapt to the changes.
If needed, please also prepare PRs on documentation-website changes as part of the 3.0 release process.
Overall, this would help us deliver a smooth and seamless upgrade experience.
Thanks.
The text was updated successfully, but these errors were encountered: