Skip to content
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

Audit - Always run Applicability Scan if CVE discovered #37

Merged
merged 10 commits into from
Apr 15, 2024

Conversation

attiasas
Copy link
Contributor

@attiasas attiasas commented Mar 12, 2024

  • The pull request is targeting the dev branch.
  • The code has been validated to compile successfully by running go vet ./....
  • The code has been formatted properly using go fmt ./....
  • All static analysis checks passed.
  • All tests have passed. If this feature is not already covered by the tests, new tests have been added.
  • All changes are detailed at the description. if not already covered at JFrog Documentation, new documentation have been added.

With the new statuses, we no longer need to stop running applicability if not supported, it will show 'NOT SCANNED'

depends on:
#36

Update dependencies:
Core -> v2.51.0
Client-go -> v1.40.1

@attiasas attiasas added the improvement Automatically generated release notes label Mar 12, 2024
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Mar 12, 2024
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Mar 12, 2024
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Mar 12, 2024
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Mar 12, 2024
Copy link

👍 Frogbot scanned this pull request and found that it did not add vulnerable dependencies.


@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Apr 2, 2024
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Apr 2, 2024
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Apr 15, 2024
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Apr 15, 2024
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Apr 15, 2024
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Apr 15, 2024
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Apr 15, 2024
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Apr 15, 2024
Copy link

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


@attiasas attiasas merged commit 9fe5147 into jfrog:dev Apr 15, 2024
8 of 9 checks passed
@attiasas attiasas deleted the remove_ca_not_support branch April 15, 2024 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Automatically generated release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants