Planned breaking changes for v2.0.0

📝 Major v2.0.x release cleanup: breaking changes and code removal

This issue serves as the central hub for tracking all planned code removals and intentional breaking changes for k6 next major release v2.0.0. As a part of our stability guarantees, we reserve major releases for introducing planned breaking changes. This ensures our users have a predictable and stable experience with minor and patch releases, while also allowing us to evolve the codebase, remove technical debt, and introduce significant improvements.

⚠️ Planned breaking changes

This section documents the specific breaking changes and outlines the plan for how we'll integrate them and communicate them to our users.

While creating the specific sub-issue make sure to add the following items as acceptance criteria:

Create a PR to implement the change
Update internal documentation
Draft a communication plan for users

@codebien

Hi @codebien,

I've created PRs for the first two sub-issues in this epic:

Completed

Remove the deprecated k6 login [cloud / influxdb] command #5115 - Remove deprecated k6 login [cloud / influxdb] command
- PR: feat: remove deprecated k6 login command #5134
- Status: Ready for review
Remove the deprecated k6 cloud script.js command #5116 - Remove deprecated k6 cloud script.js command
- PR: feat: remove deprecated direct execution from k6 cloud command #5133
- Status: Ready for review

Questions for next actions

Should I proceed with the internal documentation updates and communication plan drafts for these two changes, or wait for PR approval first?
Are there additional breaking changes planned for v2.0.0 that aren't yet tracked as sub-issues in this epic?
Would you like me to help with any other aspects of the v2.0.0 release preparation?

Thanks for coordinating this major release effort! 🚀

@moko-poi

Hey @moko-poi,
thanks for you collaboration 🙇

Should I proceed with the internal documentation updates and communication plan drafts for these two changes, or wait for PR approval first?

Yes, you should submit a pull request. Regardless of whether your pull request is merged, we'll still require pull requests for k6-docs to explain the changes.

@heitortsergent, @oleiade we should start thinking how and where to document these changes. What are your thoughts on creating a "v2 breaking changes" page to consolidate all of them?

Are there additional breaking changes planned for v2.0.0 that aren't yet tracked as sub-issues in this epic?

Yes, there are. The first step should go over this list https://github.com/search?q=repo%3Agrafana%2Fk6+deprecate+language%3AGo&type=code&l=Go and see if we can drop something. However, I'm not sure an external contributor has enough context for doing it, however you might try submitting proposals here in the issue and we'll evaluate them.

Would you like me to help with any other aspects of the v2.0.0 release preparation?

I'm sure you can go over the list of GitHub issues and find something interesting to you. If the required outcome is not clear from the issue's description, feel free to ask in a comment directly there.

All subtasks are done so I will close this as done 🎉

Navigation Menu

Repository navigation

Planned breaking changes for v2.0.0 #5062

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Planned breaking changes for v2.0.0 #5062

Description

Activity

moko-poi commented on Sep 6, 2025

codebien commented on Sep 8, 2025

mstoykov commented on May 7, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions