Skip to content

Conversation

@EyalDelarea
Copy link
Contributor

@EyalDelarea EyalDelarea commented Apr 20, 2025

  • All tests passed. If this feature is not already covered by the tests, I added new tests.
  • I used npm run format for formatting the code before submitting the pull request.

Why

This PR downgrades the default JFrog CLI version used in the action to avoid breaking existing workflows that rely on the setup-jfrog-cli step outputs — specifically those related to OIDC authentication.

In recent CLI versions, the OIDC token exchange logic was moved inside the CLI itself. As a result, the access token is no longer exposed via step outputs, which broke pipelines that depended on this behavior.

What’s Changing

  • Downgrade the default CLI version to restore the previous behavior where the access token is available as a step output.

@EyalDelarea EyalDelarea added bug Something isn't working safe to test Approve running integration tests on a pull request labels Apr 20, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Apr 20, 2025
@EyalDelarea EyalDelarea added the safe to test Approve running integration tests on a pull request label Apr 20, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Apr 20, 2025
@EyalDelarea EyalDelarea merged commit 611876c into jfrog:master Apr 20, 2025
23 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant