k6 release v2.3.0

Release Date:

21st September 2026

Release Activities

At the beginning of the cycle

• Create a new release-v2.3.0 branch.
  • Add a new v2.3.0.md release notes file using the available template to the repository's release notes folder.
• Create a new release-v2.3.0 branch on the grafana/k6-DefinitelyTyped fork repository.

  • Branch off upstream/master, not the fork's master. The fork's master is an old copy of upstream. Do not use GitHub's "Sync fork" button: repository rules on the fork block it and they cannot be amended.

    bash复制

    git remote add upstream https://github.com/DefinitelyTyped/DefinitelyTyped.git  # only once
    git fetch origin && git fetch upstream
    git checkout -b release-v2.3.0 upstream/master
    git push -u origin release-v2.3.0

  • Bump the version in types/k6/package.json to 2.3.9999.

• Lock the conversation of the current issue to prevent any abuse or misuse of the issue. Note, it still allow the maintainers to edit the issue's description and to add comments.

Release Preparation

~ 2 weeks before the release date

• Ensure that all PRs from a release milestone are merged.

~ 1 week before the release date

• Ensure that all merged PRs referenced in the release notes are linked to the release milestone.
• 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
  • Ask teams that might have contributed to the release to contribute their notes and review the existing ones.
  • Remember to mention and thank external contributors.
• Share the release notes PR with the k6 open-source teams. Request contributions from all affected teams and any other stakeholders involved in the new release.
• Open a separate PR for bumping the k6 version to 2.3.0.
• Open a PR in the DefinitelyTyped/DefinitelyTyped repository using the release-v2.3.0 branch created in the grafana/k6-DefinitelyTyped fork to update the k6 type definitions for the new release.
• Open a PR to add the new k6 version to the extensions registry, adding - v2.3.0 under versions: in registry-v2.yaml (similar to this one for v2.2.0). Register k6 v2.3.0. Merge only after the k6 v2.3.0 release is published.

~ 1 day 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 merged.

Release Day

Documentation

• Open and merge a PR from main in the k6-docs repository:
  • Creating a new v2.3.0.md file in the next release notes folder and copy/paste the main sections of the release notes (new features, deprecations and roadmap).
  • Copying the current k6's next (including the newly created release note file) to a folder named with the k6 version, v2.3.x.
• Ensure the k6 repository release notes PR contains the correct links to the docs.

In k6 repository

• Merge the PR bumping the k6 version to 2.3.0.
• Merge the release notes PR.
• Pull locally the previously merged changes.
• Create a new long-lived v2.3.x release branch from the master branch.
• Create and push a new tag of the form v2.3.0.

git checkout master && git pull && git checkout -b v2.3.x && git push -u origin v2.3.x && git tag v2.3.0 -m "v2.3.0" && git push origin v2.3.0

In k6-extension-registry

• After the k6 v2.3.0 release is published, merge Register k6 v2.3.0. Note: v2 versions live in registry-v2.yaml, not registry.yaml.
• Push a new tag/make new release to push that the update to production

Announcements

• Notify the larger team in the #k6 and #k6-changelog channels, letting them know that the release is published by linking the release on GitHub.
• 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.