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
As of Dec 1st, the GitHub actions pipelines using set-env were failing due to the change in the GitHub actions handling the environment vars.
version used: jfrog/setup-jfrog-cli@v1.0.5
Does the latest version of the jfrog action support environment files or is it still using set-env ? below are some of the failures noticed with the rt upload.
The text was updated successfully, but these errors were encountered:
@manuchandrasekhar
This issue is already resolved in the latest version v1.1.0. Feel free to upgrade.
Explanation
Before 1.1.0, we used @actions/core dependency v1.2.1. As can be seen here, this issue is resolved in @actions/core v1.2.6. Therefore in setup-jfrog-cli v1.1.0 we upgraded @actions/core to v1.2.6.
We'd appreciate your feedback on that.
By the way, to constantly receive our latest non-breaking changes and fixes, you can use the @v1 tag, for example:
As of Dec 1st, the GitHub actions pipelines using set-env were failing due to the change in the GitHub actions handling the environment vars.
Does the latest version of the jfrog action support environment files or is it still using set-env ? below are some of the failures noticed with the rt upload.
The text was updated successfully, but these errors were encountered: