Add an “About API versioning” cookbook page #452
Conversation
|
I’ll add something to support API evolution in 2.3 or 2.4. Can we hold this PR until it is ready? |
|
Thanks so much for your PR and the time you invested in contributing to this project! We truly appreciate your effort and involvement. Unfortunately, we must close this PR because the codebase has changed significantly since your submission. However, we’d love to see your contributions in the future! If you’re interested, feel free to check out the latest branches (refer to our Maintenance Guide) where your input would be very welcome. Thanks again and we hope to see you around the project soon! |
|
🤣 Thank you for taking time to add a nice note when closing this PR! See y’all one day :) |
See you soon! 😀 |
Add a very basic page in core conveying this message:
I’m a little concerned that this page is quite blunt, I would rather soften the message somehow.
Maybe something like “API versioning is not managed for now, the current recommended way is to create a new project”. But then I would be concerned that it could be interpreted as some broken promise 🤷♀️
closes #451