You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have monorepo with couple of apps/libs.
When executing npx nx affected --target=publish --base=master it's running publish target for each affected applicaton.
Hey @xiongemi ,
Issue is still reproducable with nx 19.2.3.
Please, try to clone https://github.com/izaneuski/nx-test
switch to test/nx branch
and run npx nx affected --target=publish-test --base=main --verbose
This pr is meant to replace #22585 and
#20524
Env variables using other variables were not unloaded from the
environment and further customizations were impossible in more specific
env files.
<!-- Please make sure you have read the submission guidelines before
posting an PR -->
<!--
https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr
-->
<!-- Please make sure that your commit message follows our format -->
<!-- Example: `fix(nx): must begin with lowercase` -->
## Current Behavior
<!-- This is the behavior we have today -->
## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->
## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->
Fixes#23581
Co-authored-by: Mateo Tibaquira <nestormateo@gmail.com>
(cherry picked from commit 88fd03b)
Current Behavior
We have monorepo with couple of apps/libs.
When executing
npx nx affected --target=publish --base=master
it's runningpublish
target for each affected applicaton.Each app use own envFile in config, despite that all affected runs
nx run app:publish
use same envFile(first nx affected in list)Expected Behavior
Each app gets own variables from
envFile
GitHub Repo
No response
Steps to Reproduce
.tmp/apps/app1.env:
.tmp/apps/app2.env:
app1:
app2:
npx nx affected --target=publish-test --base=master --verbose
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: