-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
k6 release v0.51.0 #3662
Comments
The release branch for v0.51.0 has been created. |
Pull request to bump the dependencies has been created #3663 |
DefinitelyTyped branch release-v0.51.0 has been created. |
This was referenced Apr 29, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Release Date:
20th May 202413th May 2024 (the team decided to anticipate one week)Release Activities
At the beginning of the cycle
@k6-browser
team and co-assign the issue to them.release-v0.51.0
long-lived branch and add a new release notes file using the available template to the repository'srelease notes
folder.release-v0.51.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.~ 1 day before the release date
k6-docs
repository, related to new or modified functionalities introduced by the new version have been merged.Release 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.51.0 -m "v0.51.0"
.Announcements
Wrapping Release
DefinitelyTyped/DefinitelyTyped
PR(s) are merged..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: