feat: add attestations, annotations, and labels to image #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the GitHub Actions workflow for the release process by enhancing the Docker build steps with additional metadata and security features. The most important changes include adding OCI labels and annotations, enabling SBOM generation, and setting provenance mode to maximize build traceability.
Enhancements to Docker build steps:
.github/workflows/release.yml: Added a step to include OCI labels using thedocker/metadata-action@v5action, which generates metadata for Docker images..github/workflows/release.yml: Updated the Docker build step to include annotations and labels from the OCI metadata step, enabled SBOM generation for software bill of materials, and set provenance mode tomaxfor enhanced traceability.Attestations are cryptographically signed metadata that somehow aid in supply chain security. Annotations add metadata to the registry (i.e. ghcr.io). Labels add metadata to the image itself.