Automate release pages
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, javascript
Research direction
Start by reading assets/js/releaseData.js and break the request into a specific release, beta, or alpha workflow before making changes. The issue mentions GitHub APIs, GitHub Actions, a /builds page, and several distribution targets, but does not identify tests or a bounded first milestone; done would require an agreed scope and the corresponding checklist items completed.
Written by the indexing model from the issue text.
Description
Currently, releases need to be updated by hand via assets/js/releaseData.js. Additionally, alphas and betas aren't represented at all. We could automate this.
Alphas
- Get an API which gets the latest build from Github and offers it to download (similar to https://github.com/oprypin/nightly.link )
- Do the same for the qt branch once that's testing-ready
- Create a /builds page on which they can live (similar to https://builder.blender.org/download/daily/)
Betas
- Create a GH action which publishes a beta release on Github
- and enables temporary elements to the homepage pointing towards the beta
Releases
- Create a GH action which publishes releases to
- winget
- Github releases
- musehub
- Fosshub
- MS store
- (if legally possible) Apple App store
- (if we want to maintain it) Snapcraft
- (if we want to maintain it) Flathub
- updates releaseData.js
- and hides the temporary beta element from the homepage
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 8
- Avg merge
- 21m
- Merged PRs (30d)
- 6
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.
More from audacity/audacity.github.io
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
audacity/audacity.github.io#105 · 1 reaction ·
-
Dead links Open
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Add license Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
No checksum type Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
audacity/audacity.github.io#41 · 1 reaction ·
All issues in audacity/audacity.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/inspector#2458 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
railmapgen/rmp-gallery#4068 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·