--version flag being set to false even when providing value
See original GitHub issueFollowing the directions in the readme, I am attempting to update the versions for my affected projects.
nx affected --target version --version=prerelease --preid=alpha
The nx console then always shows that the --version flag has been set to false even though prerelease has been provided as a value.
> NX Running target version for 7 project(s):
- component-tester
- component-tester-e2e
- documentation-e2e
- documentation
- navigation
- scss-commons
- ui-commons
With flags:
--version=false
--preid=alpha
Running the version command on a specific project nx run my-project:version [...options] seems to work fine
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
version flag being set to false even when providing value #218
I'm having the same issue. Just some quick tinkering makes it look like it's butting up against the --version flag that exists for...
Read more >bool flag set to false even though XML Element Exists
I am using a bool flag to check to make sure XML Elements exist before writing them to a variable. The problem is...
Read more >Creating flag variations - LaunchDarkly docs
Boolean flags have two variations: true or false . ... After a feature flag has been created, you cannot change the type of...
Read more >How To Use Gflags (formerly Google Commandline Flags)
If it returns false for the default value, ParseCommandLineFlags will die. Here is an example use of this functionality:
Read more >GitLab Runner feature flags
Feature flag Default value Deprecated
FF_CMD_DISABLE_DELAYED_ERROR_LEVEL_EXPANSION false No
FF_NETWORK_PER_BUILD false No
FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY false No
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Hi, this should be fixed in 2.8.1 using
--releaseAs=...instead of--version=....I’m also running into this when trying to use
nx affectedto version all packages that have been changed. Falling back to a script that uses--plainas recommended by @CaffeinatedCodeMonkey but it would be awesome if this worked out of the box