Automate release pages #12

Open
opened 2025-09-09 19:41:42 -05:00 by Octech6711 · 0 comments
Owner

Originally created by @LWinterberg on GitHub.

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

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
Originally created by @LWinterberg on GitHub. 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 - [x] 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
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: audacity/audacity.github.io#12
No description provided.