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
I'm maintaining a package that is an augmented version of an existing library. A bit like a fork ; I constantly add their modifications into my project, but I cannot just merge their commit.
For this reason, I have added their repo as a remote in my project, it makes things easier for me. Except for the part that I don't use their tags and they mess with my changelog tooling.
Current Behavior
When using lerna publish, it creates a tag for the new version and pushes it along with tags from others remotes.
Expected Behavior
I expected lerna to only push the tag it created.
Steps to Reproduce
Create one repo using lerna, and another one without, and publish them on GH.
Now create a tag v1 on the first repo and v2 on the second repo. Push those tags to their respective remote.
In the first repo, add the second repo as a git remote.
Make some changes in the first repo, and run lerna publish.
🪄 you know have a tag v2 on your first repo.
I'm maintaining a package that is an augmented version of an existing library. A bit like a fork ; I constantly add their modifications into my project, but I cannot just merge their commit.
For this reason, I have added their repo as a remote in my project, it makes things easier for me. Except for the part that I don't use their tags and they mess with my changelog tooling.
Current Behavior
When using
lerna publish
, it creates a tag for the new version and pushes it along with tags from others remotes.Expected Behavior
I expected lerna to only push the tag it created.
Steps to Reproduce
Create one repo using lerna, and another one without, and publish them on GH.
Now create a tag
v1
on the first repo andv2
on the second repo. Push those tags to their respective remote.In the first repo, add the second repo as a git remote.
Make some changes in the first repo, and run
lerna publish
.🪄 you know have a tag
v2
on your first repo.Environment
Environment info:
System:
OS: macOS 14.3.1
CPU: (12) arm64 Apple M2 Max
Binaries:
Node: 18.13.0 - ~/.nvm/versions/node/v18.13.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v18.13.0/bin/yarn
npm: 8.19.3 - ~/.nvm/versions/node/v18.13.0/bin/npm
Utilities:
Git: 2.39.3 - /usr/bin/git
npmPackages:
lerna: ^8.1.2 => 8.1.2
The text was updated successfully, but these errors were encountered: