Update slsa-framework/slsa-github-generator action to v1.4.0 #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
MarcelRaschke
approved these changes
Dec 14, 2022
delete-merged-branch
bot
deleted the
renovate/slsa-framework-slsa-github-generator-1.x
branch
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR contains the following updates:
v1.2.0->v1.4.0Release Notes
slsa-framework/slsa-github-generator
v1.4.0Compare Source
What's Changed
🥳 This release is the first Generally Available version of the Container Generator workflow. The Container Generator workflow is now considered stable and can be included in your production GitHub Actions workflows 🥳
🎉 This is also the first release (technically the second) with support for the generally available version of sigstore!! 🎉
We hope to have fewer issues with sigstore infrastructure moving forward.
Generic Generator
Bug fixes
Go Builder
Bug fixes
New Contributors
Full Changelog
v1.3.0Compare Source
🚨⚠️ This is a release and tag that was created as a pre-release for testing purposes and is not supported. DO NOT UPGRADE. If you have already upgraded please downgrade to v1.2.2 ⚠️ 🚨
See: #1250
v1.2.2Compare Source
What's Changed
This release fixes issues with signing provenance due to a change in Sigstore TUF root certificates (#1163). This release also includes better handling of transient errors from the Rekor transparency logs.
New Contributors
Full Changelog
cb0f703by @renovate-bot in https://github.com/slsa-framework/slsa-github-generator/pull/10625759d19by @renovate-bot in https://github.com/slsa-framework/slsa-github-generator/pull/1201v1.2.1Compare Source
🚨⚠️ DO NOT USE THIS RELEASE. This version will no longer work and is not supported due to errors described in #1163. Please upgrade to v1.2.2 or later. ⚠️ 🚨
What's Changed
This release fixes an error that occurs on the "Generate Builder" step for various workflows.
See #942
Generic generator
buildType
This release changes the
buildTypeused in provenance created by the generic generator.The previous value was:
The new value is:
See #627
Provenance file names
Previously the default file name for provenance was
attestation.intoto.jsonl. This has been updated to be in line with intoto attestation file naming conventions. The file name now defaults to<artifact filename>.intoto.jsonlif there is a single artifact, ormultiple.intoto.jsonlif there are multiple artifacts.See #654
Explicit opt-in for private repos
Private repository support was enhanced to required the
private-repositoryinput field as the repository name will be made public in the public Rekor transparency log.Please add the following to your workflows if you opt into allowing repository names to be recorded in the public Rekor transparency log.
See #823
Go builder
Support private repos
Support for private repositories was fixed. If using a private repository you must specify the
private-repositoryinput field as the repository name will be made public in the public Rekor transparency log.Please add the following to your workflows if you opt into allowing repository names to be recorded in the public Rekor transparency log.
See #823
New Contributors
Full Changelog
build:idin generic examples by @laurentsimon in https://github.com/slsa-framework/slsa-github-generator/pull/596128564fby @renovate-bot in https://github.com/slsa-framework/slsa-github-generator/pull/6209349ed8by @renovate-bot in https://github.com/slsa-framework/slsa-github-generator/pull/557f4787e8by @renovate-bot in https://github.com/slsa-framework/slsa-github-generator/pull/838f213421by @renovate-bot in https://github.com/slsa-framework/slsa-github-generator/pull/8417292458by @renovate-bot in https://github.com/slsa-framework/slsa-github-generator/pull/972b44042aby @renovate-bot in https://github.com/slsa-framework/slsa-github-generator/pull/973Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.