8000 Fix breaking change after Security CLI SCA changes by attiasas · Pull Request #879 · jfrog/frogbot · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fix breaking change after Security CLI SCA changes #879

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 8 commits into
base: dev
Choose a base branch
from

Conversation

attiasas
Copy link
Contributor
@attiasas attiasas commented Jun 29, 2025
  • All tests passed. If this feature is not already covered by the tests, I added new tests.
  • This pull request is on the dev branch.
  • I used gofmt for formatting the code before submitting the pull request.
  • Update documentation about new features / new supported technologies

Depends on:

@attiasas attiasas added safe to test Approve running integration tests on a pull request ignore for release Automatically generated release notes labels Jun 29, 2025
@attiasas attiasas requested a review from eranturgeman June 29, 2025 14:13
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Jun 29, 2025
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Jun 29, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Jun 29, 2025
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Jun 29, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Jun 29, 2025
go.mod Outdated
@@ -118,7 +118,8 @@ require (
gopkg.in/warnings.v0 v0.1.2 // indirect
)

replace github.com/jfrog/jfrog-cli-security => github.com/jfrog/jfrog-cli-security v1.19.1-0.20250625095826-3aba9954dfc9
//attiasas:sca_scan_interface
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't we wait for the merge to dev? if so - let's redirect and run tests again

@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Jun 29, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Jun 29, 2025
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Jun 30, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Jun 30, 2025
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Jul 1, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Jul 1, 2025
@attiasas attiasas changed the title Fix breaking change after merge Sca scan interface Fix breaking change after Security CLI SCA changes Jul 2, 2025
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Jul 4, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Jul 4, 2025
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Jul 4, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Jul 4, 2025
Copy link
Contributor
github-actions bot commented Jul 4, 2025

👍 Frogbot scanned this pull request and did not find any new security issues.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ignore for release Automatically generated release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0