semantic-release / semantic-release/github
support for artifact attestations
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
now that the capability is available in beta, i want to start looking into what it would take to support through semantic-release
https://github.blog/changelog/2024-05-02-artifact-attestations-public-beta/
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 with the linked GitHub artifact attestations public-beta changelog, then inspect the semantic-release GitHub plugin's release flow. Define the required support and concrete acceptance criteria before changing code; the issue currently names no files, tests, or expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100