k6 release v1.0.0-rc1

[codebien]

Release Dates:

24th Mar 2025

Release Activities

At the beginning of the cycle

• Create a new release-v1.0.0-rc1 branch.
  • 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.
  • Bump buf.build/prometheus #4553
  • Bump x509roots #4552
  • Bump the otel group with 6 updates #4215
  • Bump the googles group across 1 directory with 4 updates #4526
  • build(deps): bump the golangx group across 1 directory with 7 updates #4550
  • Bump github.com/evanw/esbuild from 0.24.2 to 0.25.0 #4527
  • Upgrade OpenTelemetry to v1.34 #4578
• Create a new release-v1.0.0-rc1 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 PRs from a release milestone are merged.
• Ensure experimental modules (if needed) have been updated to their latest version.

~ 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 (e.g., k6-ecosystem, k6-docs, k6-devrel teams) 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 PR 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.
  • [@types/k6] Update k6 for the latest version v1.0.0 DefinitelyTyped/DefinitelyTyped#72052

~ 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, 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 v1.0.x release branch from the main branch.
• Checkout the new v1.0.x release branch, create and push a new tag of the form v1.0.0-rc1 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.