Enable immutable releases
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
This action should enable immutable releases to help protect users against potential attacks such as GHSA-mrrh-fwg8-r2c3 by preventing re-pointing (released) tags to different commits.
Contributor guide
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 reading the linked GitHub immutable releases documentation and inspecting this repository's release and tag configuration. Determine where the action's release process is defined and verify that released tags cannot be re-pointed; done means the repository uses immutable releases without breaking its existing release workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100