specify version resolution via api / respect registry versions #22891
ryanbas21
started this conversation in
Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I don't see a current way to specify version resolution through the nx release api.
My use case is i have a verdaccio server running on a different computer that my team shares.
I also publish to npm and maybe i want to follow tags in this case.
I can use git-tags but then id have to push tags for the dev env as well (verdaccio server) or keep the package.json updated constantly. if i could specify registry and nx release would then look at the registry i defined in my api script, then it can look and see what tag / version i need that would be super cool.
if there is a way to do this already maybe i just dont see it! I suppose i could use registry if the nx api respected the registry i currently was using instead of just npm every time.
It also seems that nx release version resolution to npm itself doesnt fully respect beta tags. for example i have published a few beta tags with a specifier like v4.4.1-beta.5 but nx release if i set the value in nx.json to "registry" resolves:
it also seems to only check
npm
for this instead of the verdaccio server:even though in my script i've set the registry to my verdaccio deployment.
If i am trying to resolve a beta tag from npm and specify the
npm registry
it obviously looks atnpm
but it doesnt seem to respect the versions ive published:even though i have 4.4.1-beta.1/2/3/4/5 published
So ideally: i could just use
registry
and nx release respects the registry i am using - then can properly resolve the version from that registry or i can specifygit-tag
orregistry
within the api.Beta Was this translation helpful? Give feedback.
All reactions