-
Notifications
You must be signed in to change notification settings - Fork 83
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update content/en/system_config/integration.md
Co-authored-by: ltagliaferri <[email protected]> Signed-off-by: jonvnadelberg <[email protected]>
- Loading branch information
1 parent
e10ecf5
commit 2a5c3ff
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,7 +20,7 @@ A package manager looking to adopt Sigstore as part of its artifact signing and | |
5. Once RFC proposal is approved per community norms, drive implementation plan | ||
6. Work to drive initial package adoption strategy; this often involves highly visible or valuable packages that can serve as references for other package maintainers within the ecosystem | ||
7. Work with popular build and packaging extensions (like GoReleaser, JReleaser) and builder templates (Jenkins plugins, GitHub Actions) | ||
8. Release all code & service extensions required for Sigstore support in a fully-supported mode | ||
8. Release all code and service extensions required for Sigstore support in a fully-supported mode | ||
9. Presuming success to this point, set date for mandating Sigstore signing and verification for all packages in ecosystem | ||
Check failure on line 24 in content/en/system_config/integration.md GitHub Actions / markdownlintTrailing spaces
|
||
|
||
Integrating Sigstore with your own applications provides an effective way to enhance security: | ||
|