k6 release v0.56.0

[ankur22]

Release Date:

06th Jan 2025

Release Activities

At the beginning of the cycle

• Create a new release-v{major}.{minor}.0 branch and add a new release notes file using the available template to the repository's release notes folder.
• Go through the potential dependencies updates and create a dedicated PR if any of them is relevant to this release.
• Create a new release-v{major}.{minor}.0 branch on the grafana/k6-DefinitelyTyped fork repository.
  • Bump the version in types/k6/package.json to the next one.

Release Preparation

~ 2 weeks before the release date

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

~ 1 week before the release date

• Ensure that all merged pull-requests referenced in the release notes are linked to the release milestone.
• Ensure all pull-requests in the k6-docs repository, related to new or modified functionalities introduced by the new version have been created.
• Ensure all PRs in the k6 repository, part of the current milestone, have been merged.
• Open a PR with the release notes for the new version
  • Ask teams who might have contributed to the release (k6-ecosystem, k6-docs, k6-devrel teams, etc.) to contribute their notes and review the existing ones.
  • Remember to mention and thank external contributors. <-- Update the query with the correct milestone version.
• Share the release notes PR with the k6 open-source teams. Request contributions from all affected teams (k6-chaos, k6-docs, k6-devrel, etc.) and any other stakeholders involved in the new release.
• Open a separate pull-request for bumping the k6 Go project's version.
• 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.

~ 1 day before the release date

• 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

• Open and merge a pull-request from master in the k6-docs repository, copying the current k6's next to a folder named with the k6 version (e.g. v0.55.x).
• Ensure the k6 repository release notes PR contains the correct links to the docs.

In k6 repository

• Merge the PR bumping the k6 Go project's version.
• Merge the release notes PR.
• Pull locally the previously merged changes.
• Create a new long-lived v{major}.{minor}.x release branch from the master branch.
• Checkout the new v{major}.{minor}.x release branch, create and push a new tag of the form v{major}.{minor}.0 using git: e.g. git tag v0.55.0 -m "v0.55.0".

Announcements

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

Wrapping Release

• Ensure the DefinitelyTyped/DefinitelyTyped PR(s) are merged.
• Update the k6 repository's .github/ISSUE_TEMPLATE/release.md in the event steps from this checklist were incorrect or missing.