feat(publish): replace +{SHA} with .{SHA} in lerna publish --canary#4124
feat(publish): replace +{SHA} with .{SHA} in lerna publish --canary#4124MatusKnizka wants to merge 2 commits intolerna:mainfrom
Conversation
|
View your CI Pipeline Execution ↗ for commit 64ae261.
☁️ Nx Cloud last updated this comment at |
|
I'm really sorry for the delay on a formal resolution here @MatusKnizka. This is not a PR we can proceed with directly because it's mixing a couple of different concerns IMO and is a breaking change which would required wider clean up. The Importantly, it is just metadata and not used to differentiate versions during installs and dependency resolution:
Therefore, it does make sense that jfrog is "cutting it" as you describe. Please can you share more about your use-case? Are you trying to publish over the same version with different build metadata? Are you saying that lerna is not incrementing the |
Replace +{SHA} with .{SHA} in lerna publish --canary
Description
Instead of using plus (+) sign in package name provided by --canary flag, use dot.
Motivation and Context
It's not possible to publish --canary version into jfrog artifactory, as jfrog is cutting part of filename, due to + (plus) character. So, instead of using +, I would suggest to use dot.
#2060
How Has This Been Tested?
Unit tests
Integration tests
Run publish command
Types of changes
Checklist: