Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Rename "wasmer run-unstable" to "wasmer run" #3801

Closed
Michael-F-Bryan opened this issue Apr 20, 2023 · 0 comments · Fixed by #3924
Closed

Rename "wasmer run-unstable" to "wasmer run" #3801

Michael-F-Bryan opened this issue Apr 20, 2023 · 0 comments · Fixed by #3924
Assignees
@Michael-F-Bryan
Labels
🎉 enhancement New feature! 📦 lib-cli About wasmer-cli priority-medium Medium priority issue
Milestone
v4.0

Comments

@Michael-F-Bryan
Copy link
Contributor

Motivation

We introduced a wasmer run-unstable command when we rewrote the wasmer run code as part of the 3.2.0 release (#3650). By the time 4.0 comes out we should have had plenty of time to test this command and promote it to "stable".

Proposed solution

Delete the existing wasmer run command and rename wasmer run-unstable to wasmer run.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Michael-F-Bryan Michael-F-Bryan

Labels
🎉 enhancement New feature! 📦 lib-cli About wasmer-cli priority-medium Medium priority issue
Projects
None yet
Milestone
v4.0
Development

Successfully merging a pull request may close this issue.

Rename "wasmer run-unstable" to "wasmer run" wasmerio/wasmer
1 participant
@Michael-F-Bryan