k6 release v0.47.0

[codebien]

Release Date:

9th October 2023

Release Activities

At the beginning of the cycle

• Create a new release-notes-v0.4x.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.

Release Preparation

~ 1 week before the release date.

• Ensure all PRs 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, and ask teams who might have contributed to the release (@k6-browser, @k6-chaos, @devrel teams, etc.) to contribute their notes and review the existing ones.
• Share the release notes PR with the k6 open-source teams. Request contributions from all affected teams (browser, chaos, devrel, docs, etc.) and any other stakeholders involved in the new release.
• Open a separate PR for bumping the k6 Go project's version.
• Create a dedicated branch for the upcoming version in the grafana/k6-DefinitelyTyped fork repository.
• Open a PR in the DefinitelyTyped/DefinitelyTyped repository, using the branch created in the grafana/k6-DefinitelyTyped fork, to update the k6 type definitions for the new release.
  • [k6] Add context.cookies and improve cookie TS definitions DefinitelyTyped/DefinitelyTyped#66909
  • Add page.on('console') method definition for k6/experimental/browser DefinitelyTyped/DefinitelyTyped#66549
  • k6 Version/0.47 k6-DefinitelyTyped#15

~ 1 day before the release date.

• Open a PR in the k6-docs repository, archiving the current k6's JavaScript API version as per the following instructions.
  • Docs for v0.47.0 k6-docs#1367
• Ensure the existing k6-docs PRs, related to the new functionalities and changes, are reviewed, up to date with the latest state of the master branch, and based upon the branch containing the k6 archived JavaScript API documentation (as created in the previous step).
  • gRPC's connection reflectMetadata k6-docs#1340
  • Document gRPC's -bin metadata k6-docs#1341
  • Update metric name restrictions k6-docs#1331
  • Docs: k6 browser v1.1.0 - k6 v0.47.0 k6-docs#1309

Release Day

Documentation

• Merge the k6-docs repository's Javascript API archiving PR and rebase the rest of the branches meant for the release on top of the new state of the master branch.
• Merge all the k6-docs repository's branches containing changes related to the release.
• Ensure the last resulting k6-docs GitHub action targetting the main branch sees its "Check broken links" job pass.
  • There are broken links, notified the author of an on going PR.
• Publish the new vX.Y.Z version of docs.
• 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.
• Create and push a new tag of the form vX.Y.Z using git: git tag v0.4x.0 -m "v0.4x.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.
• Close the k6-docs'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.

[codebien]

The branch https://github.com/grafana/k6/tree/release-notes-v047 has been created

[codebien]

Created https://github.com/grafana/k6/tree/release-notes-v0.47.0 and deleted release-notes-v047 for aligning to the new steps.