-
Notifications
You must be signed in to change notification settings - Fork 20
Comparing changes
Open a pull request
base repository: snyk/snyk-gradle-plugin
base: v4.0.1
head repository: snyk/snyk-gradle-plugin
compare: main
- 12 commits
- 52 files changed
- 6 contributors
Commits on Jan 17, 2024
-
fix: Use complete project path when filtering subprojects (#278)
fix: complete proj path on subprojects filtering Co-authored-by: damian <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for e216d5c - Browse repository at this point
Copy the full SHA e216d5cView commit details
Commits on Jan 22, 2024
-
Configuration menu - View commit details
-
Copy full SHA for a121cc1 - Browse repository at this point
Copy the full SHA a121cc1View commit details
Commits on Jun 5, 2024
-
Configuration menu - View commit details
-
Copy full SHA for b4c107b - Browse repository at this point
Copy the full SHA b4c107bView commit details
Commits on Sep 12, 2024
-
feat: Update CI Window Machine (#289)
* feat: update ci windows image and java selection * feat: update test to check gradle version
Configuration menu - View commit details
-
Copy full SHA for 628c688 - Browse repository at this point
Copy the full SHA 628c688View commit details
Commits on Sep 30, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 756bc8e - Browse repository at this point
Copy the full SHA 756bc8eView commit details
Commits on Oct 1, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 4a69447 - Browse repository at this point
Copy the full SHA 4a69447View commit details
Commits on Oct 3, 2024
-
feat: handle gradle wrapper files for windows (#292)
* feat: handle gradle wrapper files for windows * feat: updated test wrapper tests * feat: add test for generateWrapperProcessArgs * fix: lint files
Configuration menu - View commit details
-
Copy full SHA for 2f5ee75 - Browse repository at this point
Copy the full SHA 2f5ee75View commit details
Commits on Oct 21, 2024
-
Configuration menu - View commit details
-
Copy full SHA for b73c0da - Browse repository at this point
Copy the full SHA b73c0daView commit details
Commits on Nov 19, 2024
-
feat: support verbose gradle graphs for sbom generation (#290) (#294)
* chore: update jdk8 JAVA_HOME path * feat: support verbose gradle graphs for sbom generation (#290)
Configuration menu - View commit details
-
Copy full SHA for 3c5e683 - Browse repository at this point
Copy the full SHA 3c5e683View commit details
Commits on Nov 29, 2024
-
feat: handle spawn error on gradle command (#295)
* feat: handle spawn error on gradle command * feat: set java path in ci
Configuration menu - View commit details
-
Copy full SHA for 37316ad - Browse repository at this point
Copy the full SHA 37316adView commit details
Commits on Dec 3, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 17eb0c2 - Browse repository at this point
Copy the full SHA 17eb0c2View commit details
Commits on Dec 19, 2024
-
feat: record pkg id provenance (#297)
* feat: record pkg id provenance Add pkgIdProvenance to the dep-graph nodes where the coordinate has been changed when using `--gradle-normalize-deps`. This allows users to see what the original coordinate was in dep-graph JSON output. Nodes will appear like so: ```json { "nodes": [ { "nodeId": "org.apache.logging.log4j:[email protected]", "pkgId": "org.apache.logging.log4j:[email protected]", "info": { "pkgIdProvenance": "my.logging:[email protected]", } } ] } ``` Where "my.logging:log4j" has been identified as "org.apache.logging.log4j:log4j-core". When co-ordinates have not been changed, there is no label. * test: ignore failing test Follow up in a later PR on why this test is failing since the latest release of guava. For some reason we're including the 'default' configuration when we shouldn't.
Configuration menu - View commit details
-
Copy full SHA for 9589d18 - Browse repository at this point
Copy the full SHA 9589d18View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v4.0.1...main