theupdateframework / theupdateframework/python-tuf
Use Immutable Releases
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 304
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 17
Description
There's a checkbox in the settings Enable release immutability: we should check it.
The docs are just vague enough that I'm not 100% sure if our current released workflow works with it:
- Description is "Disallow assets and tags from being modified once a release is published"
- We don't modify assets but do add them after the initial publish: I think that might still be a violation
Maybe best to tweak the release workflow so the initial publish makes the release a draft (and the final publish makes it non-draft): then we should be good to go.
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 with the repository's release workflow and review how it publishes releases and adds assets. Check GitHub's release immutability behavior, then adjust the workflow so the initial release is a draft and the final publish is non-draft. Done means the workflow completes without modifying an immutable release and all release assets are present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100