rokucommunity / rokucommunity/workflows
Build and checksum verify the release artifact during publish-release
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 26m
- Merged PRs (30d)
- 5
Description
For additional security, we should build the release artifact again at "publish-release" time, and then compare it against the copy we have in the github release. This will allow us to verify a malicious actor hasn't replaced the artifact in the github release between staging the release and publishing it.
Considerations:
- the build environment will need to be identical to the "create-release-artifacts" (or we just call it again?)
- this will "slow down" releases because it'll take the full build time to create it. (maybe we could skip the validation steps though and just to the build and package)?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the publish-release and create-release-artifacts workflows and the GitHub release artifact they produce. Determine how to rebuild and compare the artifact at publish time while preserving an identical build environment; done means publish-release verifies the staged artifact before publishing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100