new release notes layout
Adds a new utility called release-notes that I find more appealing and declarative for the end user, starting with build one. This utility can be reused by other projects. we might need to tweak a bit some fields to make it more generic and cover all use cases (cc @thaJeztah @usha-mandya):

Signed-off-by: CrazyMax [email protected]
Deploy Preview for docsdocker ready!
Built without sensitive environment variables
| Name | Link |
|---|---|
| Latest commit | 711be5460486363c6d81ed93668a5f43dca2006f |
| Latest deploy log | https://app.netlify.com/sites/docsdocker/deploys/63205792e8957000084a9f18 |
| Deploy Preview | https://deploy-preview-15291--docsdocker.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Thanks @crazy-max. The badges look neat and helps users understand the type of fix.
We have release notes for other components as well that follow a different format. We need to take a look at this a whole and see how we can be consistent across components. Before we go ahead and use this format, I'd like to review this with the team and get their input as well as it's not just Buildx docs but also affects other projects.
Made some changes to have a more generic release-notes layout so it can be used across our website:
- We can define components with their respective entries like Docker Desktop release notes does (For all platforms, For Mac, ...).
- Option to enable/disable GitHub link to full release notes
- Multiple tags support and allow arbitrary ones
- Header support to add arbitrary content before listing entries for each release
- New
upgradeandsecuritytag
I also split each release in its dedicated yaml definition. This way we could reuse this yaml file directly in Docker Desktop to display release notes for current version by just fetching it.
Here is an example with Docker Desktop 4.12 and 4.11: https://deploy-preview-15291--docsdocker.netlify.app/desktop/release-notes/

Thanks for the pull request. We'd like to make our product docs better, but havenβt been able to review all the suggestions. As our docs have also diverged, we do not have the bandwidth to review and rebase old pull requests.
If the updates are still relevant, review our contribution guidelines and rebase your pull request against the latest version of the docs, then mark it as fresh with a /remove-lifecycle stale comment.
If not, this pull request will be closed in 30 days. This helps our maintainers focus on the active pull requests.
Prevent pull requests from auto-closing with a /lifecycle frozen comment.
/lifecycle stale
/lifecycle frozen