Closed VictorRos closed 4 months ago
Hi @VictorRos , Sorry for the inconvenience caused by this issue. The regression is in 2.54.0, and the issue should be completely fixed in 2.56.0. We plan to release a new extension with the latest CLI in the upcoming days. Note that you can install a custom JFrog CLI version in the meantime using the Tools Installer Task.
Hi @VictorRos , Extension version 2.9.5 was just released and sets the default JFrog CLI version to 2.56.1. Sorry for the delay in releasing it. We'd appreciate your feedback for it.
Hi @RobiNino
I confirmed it's working again.
We removed the task JFrogToolsInstaller@1
we added temporarily to install JFrogCLI in version 2.56.0
, to let JFrogNPM@1
installed version 1.9.5
and its JFrogCLI in version 2.56.1
.
I will close the issue.
Thanks for the help for the temporary solution.
Hello!
In my Team we are using
JFrogNPM@1
to pack and publish NPM libraries.Task is failing in version
1.9.4
but works fine before that. In version1.9.4
, JFrog CLI is2.54.0
.I have this output when
JFROG_CLI_LOG_LEVEL
is set toDEBUG
.Notes:
prepare
to init Husky on local machines but not in pipelineI didn't post it as a "bug" because I saw a fix about tarball in JFrog CLI
2.56.0
that may fix this problem.Our temporary solution is to change
JFrogNPM@1
toJFrogNPM@1.9.3
.My question, when JFrogNpm@1.9.5 with JFrog CLI 2.56.0 would be available?
EDIT: Change JFrog CLI version from
2.55.0
to2.56.0