-
Notifications
You must be signed in to change notification settings - Fork 1
Add release changelogs for v0.28.0 #13
Conversation
Co-authored-by: Guillaume Mourier <[email protected]>
Co-authored-by: Guillaume Mourier <[email protected]>
Co-authored-by: Guillaume Mourier <[email protected]>
Co-authored-by: Guillaume Mourier <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's my first time editing a release changelog in a while, so I wasn't sure if I should edit things like the header levels.
On the docs we try never to use multiple H1s in the same article, or to skip a header number (i.e. don't jump from H1 to H3). But this may be an aspect of your template, so feel free to ignore those particular suggestions.
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
Co-authored-by: Tommy <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 😎
Co-authored-by: Guillaume Mourier <[email protected]>
Co-authored-by: Tommy <[email protected]>
Waiting for the last naming changes if needed on meilisearch/specifications#157 before giving a final review. Other than that, everything looks great to me! |
@gmourier I let this PR open until the official v0.28.0 is out. I've updated the PR description to make my expectations clearer |
Co-authored-by: Guillaume Mourier <[email protected]>
60a7e66
to
4ac38d9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
<!-- The following line should NOT be put in the official release changelogs --> | ||
⚠️ Since this is a release candidate (RC), the official documentation is not updated yet, but will be ready for the official v0.28.0 release. The work-in-progress documentation is available [here](). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<!-- The following line should NOT be put in the official release changelogs --> | |
⚠️ Since this is a release candidate (RC), the official documentation is not updated yet, but will be ready for the official v0.28.0 release. The work-in-progress documentation is available [here](). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So you can remove it directly from github before the release 🤓
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will not remove it from this PR, so that I can copy/paste in my next release changelog
However I will not put it in the v0.28.0 changelog on Monday haha
Here are the huge changelogs for the v0.28.0 release