k6 release v0.52.0

[joanlopez]

Release Date:

~~24th June 2024~~ 25th June 2024

Release Activities

At the beginning of the cycle

• [x] Obtain the Release coordinator's contact from the @k6-browser team and co-assign the issue to them.
• [x] Create a new release-v0.52.0 long-lived branch and add a new release notes file using the available template to the repository's release notes folder.
• [x] Go through the potential dependencies updates and create a dedicated PR if any of them is relevant to this release.
• [x] Create a new release-v0.52.0 long-lived branch on the grafana/k6-DefinitelyTyped fork repository.
  • [x] Bump the version in types/k6/package.json to the next one.

Release Preparation

~ 2 weeks before the release date

• [x] Ensure that all pull-requests from a release milestone are merged.
• [x] Ensure that browser and other experimental modules (if needed) have been updated to their latest version.

~ 1 week before the release date

• [x] Ensure that all merged pull-requests referenced in the release notes are linked to the release milestone.
• [x] Ensure all pull-requests in the k6-docs repository, related to new or modified functionalities introduced by the new version have been created.
• [x] Ensure all PRs in the k6 repository, part of the current milestone, have been merged.
• [x] Open a PR with the release notes for the new version
• [x] Ask teams who might have contributed to the release (k6-browser, k6-ecosystem, k6-docs, k6-devrel teams, etc.) to contribute their notes and review the existing ones.
• [x] Remember to mention and thank external contributors.
• [x] Share the release notes PR with the k6 open-source teams. Request contributions from all affected teams (k6-browser, k6-chaos, k6-docs, k6-devrel, etc.) and any other stakeholders involved in the new release.
• [x] Open a separate pull-request for bumping the k6 Go project's version:
  • https://github.com/grafana/k6/pull/3810
• [x] Open a PR in the DefinitelyTyped/DefinitelyTyped repository, using the release branch created in the grafana/k6-DefinitelyTyped fork, to update the k6 type definitions for the new release:
  • https://github.com/DefinitelyTyped/DefinitelyTyped/pull/69902

~ 1 day before the release date

• [x] Ensure all pull-requests in the k6-docs repository, related to new or modified functionalities introduced by the new version have been merged.

Release Day

Documentation

• [x] Open and merge a pull-request from main in the k6-docs repository, copying the current k6's next to a folder named with the k6 version (e.g. v0.48.x):
  • https://github.com/grafana/k6-docs/pull/1633
• [x] Ensure the k6 repository release notes PR contains the correct links to the docs.

In k6 repository

• [x] Merge the PR bumping the k6 Go project's version:
  • https://github.com/grafana/k6/pull/3810
• [x] Merge the release notes PR:
  • https://github.com/grafana/k6/pull/3805
• [x] Pull locally the previously merged changes.
• [x] Create and push a new tag of the form vX.Y.Z using git: git tag v0.52.0 -m "v0.52.0".

Announcements

• [x] Publish a link to the new GitHub release in the #k6-changelog channel.
• [x] Notify the larger team in the #k6 channel, letting them know that the release is published.
• [x] Close the release's milestone.

Wrapping Release

• [x] Ensure the DefinitelyTyped/DefinitelyTyped PR(s) are merged:
  • https://github.com/DefinitelyTyped/DefinitelyTyped/pull/69902
• [x] Update the k6 repository's .github/ISSUE_TEMPLATE/release.md in the event steps from this checklist were incorrect or missing.
  • [x] Renew the link to the k6 community forums, thanks to @sniku!
    • https://github.com/grafana/k6/pull/3771
  • [ ] Broken link to Dependencies.md
    • https://github.com/grafana/k6/pull/3811