Skip to content

Commit 1599716

Browse files
authored
Merge pull request #253 from smlx/update-readme
README updates and SBOM generation changes
2 parents 2ec5a87 + 4f31aa8 commit 1599716

2 files changed

Lines changed: 6 additions & 8 deletions

File tree

.goreleaser.yaml

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,11 +27,8 @@ builds:
2727
checksum:
2828
name_template: checksums.txt
2929

30-
source:
31-
enabled: true
32-
3330
sboms:
34-
- artifacts: source
31+
- artifacts: archive
3532

3633
changelog:
3734
use: github-native

README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,17 +15,18 @@ It also automatically builds and tests your code using [GitHub Actions](https://
1515

1616
## Features
1717

18-
* Use [GoReleaser](https://goreleaser.com/) to automatically build and create GitHub Releases and Docker images on merge to `main`.
18+
* Use [GoReleaser](https://goreleaser.com/) to automatically build and create GitHub Releases and container images on merge to `main`.
1919

2020
* This uses the [Conventional Commits Versioner](https://github.com/smlx/ccv) to automatically version each release.
2121

22-
* Lint your commit messages, and your Go, GitHub Action, and Dockerfile code.
22+
* Lint your commit messages, Go code, GitHub Actions, and Dockerfiles.
2323
* Test Pull Requests using `go test`.
24-
* Build Docker images from Pull Requests for manual testing and review.
24+
* Build container images from Pull Requests and push them to the GitHub container registry for manual testing and review.
2525
* Static code analysis using [CodeQL](https://codeql.github.com/) and [Go Report Card](https://goreportcard.com/).
2626
* Coverage analysis using the [go-test-coverage action](https://github.com/vladopajic/go-test-coverage).
2727
* Security analysis using [OpenSSF](https://securityscorecards.dev).
28-
* Signed binary artifacts using [artifact attestations](https://docs.github.com/en/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
28+
* Signed binary and container release artifacts using [artifact attestations](https://docs.github.com/en/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
29+
* SBOM generation for both release artifacts and container images, with image SBOMs pushed to the container registry.
2930

3031
## How to use
3132

0 commit comments

Comments
 (0)