You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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-browser, k6-ecosystem, k6-docs, k6-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 (k6-browser, k6-chaos, k6-docs, k6-devrel, etc.) and any other stakeholders involved in the new release.
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.
Release Date:
30th September 2024
Release Activities
At the beginning of the cycle
@k6-browser
team and co-assign the issue to them.release-v0.5x.0
long-lived branch and add a new release notes file using the available template to the repository'srelease notes
folder.release-v0.5x.0
long-lived branch on the grafana/k6-DefinitelyTyped fork repository.Release Preparation
~ 2 weeks before the release date
~ 1 week before the release date
k6-docs
repository, related to new or modified functionalities introduced by the new version have been created.DefinitelyTyped/DefinitelyTyped
repository, using the release branch created in the grafana/k6-DefinitelyTyped fork, to update the k6 type definitions for the new release.experimental/browser
from type definitions k6-DefinitelyTyped#63~ 1 day before the release date
k6-docs
repository, related to new or modified functionalities introduced by the new version have been merged.metadata
k6-docs#1735k6 cloud upload
command k6-docs#1734Params.discardResponseMessage
gRPC's option k6-docs#1706Release Day
Documentation
main
in thek6-docs
repository, copying the current k6'snext
to a folder named with the k6 version (e.g.v0.48.x
).In k6 repository
vX.Y.Z
using git:git tag v0.5x.0 -m "v0.5x.0"
.Announcements
Wrapping Release
DefinitelyTyped/DefinitelyTyped
PR(s) are merged.experimental/browser
from type definitions k6-DefinitelyTyped#63.github/ISSUE_TEMPLATE/release.md
in the event steps from this checklist were incorrect or missing.The text was updated successfully, but these errors were encountered: