What happened?
After a recent update to a pre-release version 0.79.2-alpha.1 (using nx release), the nxv-env-setup target started failing for all E2E tests.
After adding --verbose flag, I was able to track the source of the error to this log in nxv-pkg-install target:
NX npm error You must specify a tag using --tag when publishing a prerelease version.
What would you expect to happen?
Publishing local packages should work regardless of what the latest version is, as long as it's valid semver.
Moreover, when there's a process error that breaks execution, it should be logged regardless of whether --verbose flag is set.
What steps did you take?
In code-pushup/cli#1117:
- Updated to pre-release version with
npx nx release 0.79.2-alpha.1. (This updates version in package.json files, among other things.)
- Ran E2E tests as usual (no other changes).
See failing CI jobs.
Package version
0.0.6
What operating system are you on?
Linux
Node version
24.8.0
Relevant log output
NX npm error You must specify a tag using --tag when publishing a prerelease version.
What happened?
After a recent update to a pre-release version
0.79.2-alpha.1(usingnx release), thenxv-env-setuptarget started failing for all E2E tests.After adding
--verboseflag, I was able to track the source of the error to this log innxv-pkg-installtarget:What would you expect to happen?
Publishing local packages should work regardless of what the latest version is, as long as it's valid semver.
Moreover, when there's a process error that breaks execution, it should be logged regardless of whether
--verboseflag is set.What steps did you take?
In code-pushup/cli#1117:
npx nx release 0.79.2-alpha.1. (This updatesversioninpackage.jsonfiles, among other things.)See failing CI jobs.
Package version
0.0.6
What operating system are you on?
Linux
Node version
24.8.0
Relevant log output