v4.5.0 breaks builds due to the change in the default server ID
Closed this issue · 2 comments
Describe the bug
https://github.com/jfrog/setup-jfrog-cli/releases/tag/v4.5.0
The change to the default server ID is breaking our builds. Yes, you added 'custom-server-id' as a new parameter, but gave us no notice of a breaking change on the v4 series of the GH Action. Or the ability to pre-plan for an upgrade across our GitHub workflows.
The breaking change should have been saved until v5.
Current behavior
The default server ID now includes a slugified version of the GitHub org - repo - run ID instead of the older default value which was static across runs.
Reproduction steps
No response
Expected behavior
The change should have been made backwards compatible so that the newer default server ID value is still equivalent to the old value.
Setup JFrog CLI version
v4
JFrog CLI version
v2.72.2
Workflow operating system type and version
Ubuntu 22.04.5 LTS
JFrog Artifactory version (if relevant)
No response
JFrog Xray version (if relevant)
No response
Hi @tgharold ,
We sincerely apologize for the inconvenience caused by this error on our part.
We have just released extension version v4.5.1, which restores the default server ID while also providing the option to set a custom server ID.
Thank you for your understanding and patience.