Add SBOM release artifacts#18
Conversation
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6e36064255
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| tasks.register("releaseSbom") { | ||
| group = "distribution" | ||
| description = "Write a CycloneDX SBOM for the release runtime classpath" | ||
| outputs.file(sbomFile) |
There was a problem hiding this comment.
When releaseBundle is rerun in the same checkout after a runtime dependency changes without changing project.version, Gradle can treat releaseSbom as up-to-date because this task declares only its output and no inputs. The zip and provenance/checksum tasks may rebuild, but the old *-sbom.cdx.json remains and gets checksummed/uploaded as the release SBOM, so the published SBOM can describe the previous dependency set; declare the runtime classpath and project metadata as inputs for this task.
Useful? React with 👍 / 👎.
1 participant
Summary
Validation
./gradlew.bat check releaseBundle --no-daemon --console=plaingit diff --check