Repository navigation
Immutable Releases #2494
Replies: 2 comments 5 replies
|
Thank you for your suggestion. Given the recent supply chain attack campaigns, this is important. It's already enabled at the repository level. I'll now update all releases to make them immutable. |
|
Hi, The script appears to be moving a binary file into /usr/local/bin. Using an installation script from a remote destination in build agents is not great and not everyone can use a Docker image, yet it is proposed as the recommended approach. Moving forward, is the recommended routine pinning by (now immutable?) tag and pulling the binary directly from release? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
GitHub now allows us to prevent releases from being modified after publication (drafts are mutable), at the organization level:
https://docs.github.com/en/code-security/how-tos/secure-your-supply-chain/establish-provenance-and-integrity/preventing-changes-to-your-releases#enforcing-immutable-releases-for-your-organization
https://github.com/organizations/terraform-linters/settings/repository-defaults
This would mean that even an org administrator would be unable to overwrite the artifacts of any release after this setting is enabled.
All reactions