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
run lerna exec --since --include-merged-tags -- pwd in monorepo
lerna.json
<!-- Please paste your `lerna.json` here -->
lerna-debug.log
<!-- If you have a `lerna-debug.log` available, please paste it here -->
<!-- Otherwise, feel free to delete this <details> block -->
Context
I want run or exec command since merged tags. And lerna exec --since -- pwd will exclude other merged tags.
Why I'm not use lerna exec --since origin/master -- pwd?
It will throw errors if I add new sub-package on other branch than master, because master does not include new sub-package now.
Your Environment
Executable
Version
lerna --version
3.18.3
npm --version
6.12.0
yarn --version
VERSION
node --version
v12.13.0
OS
Version
macOS Catalina
10.15.1
The text was updated successfully, but these errors were encountered:
--include-merged-tags is only supported on lerna version (and implicitly on lerna publish and lerna changed). That it ever worked on lerna exec/lerna run is an accident of history (and never documented as such).
I guess #1712 should have added it to @lerna/filter-options as well. Or another method entirely. Or I should just give up on caring about strict(). 🤷♂
Expected Behavior
Works fine as lerna v3.16.4
Current Behavior
throw ERR! lerna Unknown arguments: include-merged-tags, includeMergedTags
Possible Solution
Steps to Reproduce (for bugs)
lerna exec --since --include-merged-tags -- pwd
in monorepolerna.json
<!-- Please paste your `lerna.json` here -->
lerna-debug.log
Context
I want run or exec command since merged tags. And
lerna exec --since -- pwd
will exclude other merged tags.Why I'm not use
lerna exec --since origin/master -- pwd
?It will throw errors if I add new sub-package on other branch than master, because master does not include new sub-package now.
Your Environment
lerna --version
npm --version
yarn --version
node --version
The text was updated successfully, but these errors were encountered: