-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add k6 upgrade
command
#3975
Comments
@mstoykov would you assign this issue to me ? |
@AkshayAwate thanks for the offer, but On the topic of the issue itself: I am not certain how useful that will be to be honest and all of the tools I can think of that do this (which is a small amoutn to be honest) are very different from k6. From downloads count some years ago, it seemed like most user either:
In all of those cases this will not be usable. I will expect this will also be major problem on MacOS and we will need to do something like running I will actually expect that we might need to do similar stuff on windows as well, although to be honest I am not very concerned with that. So from a first look this looks like functionality that will not be very used and will require platform specific solutions ... potentially multiple per platform.
cc @Llandy3d AFAIK k6-studio got autoupdate through "electron means" and actually embeds k6 inside of it. Not certain to what extend using a different k6 binary is a problem or not. Is it planned? Is it desired 🤷 From going over this I am more of the opinion that something like g (which I use, although maybe it is not needed anymore). That lets you go between versions of a given "cli app". Given that k6 still gets some breaking changes it might be better if there is a tool that does this outside of k6 and lets you use it to swap between versions. This might also be a lot less relevant with k6build and k6exec. As those likely will just build k6 versions either way. I will move this to |
Regarding the studio, I would say it wouldn't be much useful at this stage. |
Feature Description
Modern CLI tools sometimes support the option of upgrading the tool to the newest version in-place, with
upgrade
CLI command. This would allow to simplify keeping k6 up-to-date. Potentially, it might also be of use in tools like k6-studio.Suggested Solution (optional)
Running
k6 upgrade
should result in something like the following:k6
binaryAlready existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered: