-
Notifications
You must be signed in to change notification settings - Fork 246
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
The --no-default-features cli parameter was altered in 0.21.0-alpha.2 #803
Comments
Nope, thanks for reporting it. |
Related to #780 The cause for this is that the argument now is In versions of 0.20.x and before, that was only a I think it would make sense to enable the following, if possible:
The same is true for some other boolean style values. |
* Add env-var variants for the build command arguments * For boolean flags, allow non-value variant * Other minor cleanups Closes trunk-rs#803
* Add env-var variants for the build command arguments * For boolean flags, allow non-value variant * Other minor cleanups Closes trunk-rs#803
* Add env-var variants for the build command arguments * For boolean flags, allow non-value variant * Other minor cleanups Closes #803
@gzp79 The fix was released with |
One of my github action stopped working with the latest trunk version:
version:
Installed trunk 0.21.0-alpha.2.
command:
trunk build --no-default-features --features design --release -d dist/release
output:
expected behavior: it works as before
Is this change intentional ?
The text was updated successfully, but these errors were encountered: