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

chore: move release notes folder and v0.52 release notes #1644

Merged
merged 7 commits into from
Jul 19, 2024

Conversation

heitortsergent
Copy link
Collaborator

What?

Move the Release notes page from the Misc section to the top-level section, and add the release notes for the v0.52.0 of k6.

This change makes it consistent with the other Grafana products.

Checklist

  • I have used a meaningful title for the PR.
  • I have described the changes I've made in the "What?" section above.
  • I have performed a self-review of my changes.
  • I have run the npm start command locally and verified that the changes look good.
  • I have made my changes in the docs/sources/next folder of the documentation.

Related PR(s)/Issue(s)

@ppcano
Copy link
Collaborator

ppcano commented Jul 9, 2024

@heitortsergent, If we want to have a dedicated page for the release note, then, I think we should port at least the latest 6 release notes.

@heitortsergent
Copy link
Collaborator Author

@ppcano 👍. I updated the PR to include the last six release notes, would you mind taking another look? 🙇

@ppcano
Copy link
Collaborator

ppcano commented Jul 10, 2024

@heitortsergent added a commit to sort the list.

For SEO, it may be a good idea to set the canonical attribute to the release note page on GitHub. I don't know if the docs support setting the canonical metatag.

@heitortsergent heitortsergent merged commit befc5e7 into main Jul 19, 2024
5 checks passed
@heitortsergent heitortsergent deleted the chore/add-release-notes branch July 19, 2024 21:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants