We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It's better to print both the version and the git ref + date when the binary was built when printing wasmer --version
wasmer --version
The text was updated successfully, but these errors were encountered:
Yeah, this might break the wasmer --version behavior though (to upgrade wasmer). So we'll need to double check!
Sorry, something went wrong.
Things that might break: The wasmer-install process. If that works properly then we should be fine
We can have a similar thing as rustc:
➜ rustc --version rustc 1.59.0 (9d1b2106e 2022-02-23) ➜ rustc --version --verbose rustc 1.59.0 (9d1b2106e 2022-02-23) binary: rustc commit-hash: 9d1b2106e23b1abd32fce1f17267604a5102f57a commit-date: 2022-02-23 host: aarch64-apple-darwin release: 1.59.0 LLVM version: 13.0.0
Merge #3215
a846723
3215: Update wasmer --version logic, integrate wapm-cli r=Michael-F-Bryan a=fschutt - [x] Update clap - [x] Integrate wapm-cli logic - [x] Polish CLI handling and UX Fixes #3208. Fixes #3189. Co-authored-by: Felix Schütt <[email protected]> Co-authored-by: Felix Schütt <[email protected]>
e831932
fschutt
Successfully merging a pull request may close this issue.
It's better to print both the version and the git ref + date when the binary was built when printing
wasmer --version
The text was updated successfully, but these errors were encountered: