Rename project to sdvx + release CI job #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "frontend-development"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Project Rename (svdx -> sdvx):
(Sound Voltex), not SVDX.
dev.nullfragment.svdx-pico-configurator ->
dev.nullfragment.sdvx-pico-configurator.
svdx_pico_configurator_lib -> sdvx-pico-configurator +
sdvx_pico_configurator_lib.
(capabilities scope + load_config / save_config paths).
("SVDX Pico Configurator" -> "SDVX Pico Configurator").
(applications/svdx-pico -> tools/sdvx-pico) outside the commit.
Release Publishing (CI):
succeed and only on v* tag pushes.
akkuman/gitea-release-action.
.rpm globs).
come online.
Project Rename (svdx -> sdvx): - Typo fix across 32 files. The rhythm game is SDVX (Sound Voltex), not SVDX. - Tauri bundle identifier: dev.nullfragment.svdx-pico-configurator -> dev.nullfragment.sdvx-pico-configurator. - Rust crate names: svdx-pico-configurator + svdx_pico_configurator_lib -> sdvx-pico-configurator + sdvx_pico_configurator_lib. - User config dir: ~/.svdx-pico/ -> ~/.sdvx-pico/ (capabilities scope + load_config / save_config paths). - C header guard: SVDX_PICO_TYPES_H -> SDVX_PICO_TYPES_H. - All docs, plans, and product-name strings ("SVDX Pico Configurator" -> "SDVX Pico Configurator"). - Git remote updated to the new Forgejo location (applications/svdx-pico -> tools/sdvx-pico) outside the commit. Release Publishing (CI): - New release job in build.yaml runs after firmware + desktop succeed and only on v* tag pushes. - Downloads both artifacts and publishes a Forgejo release via akkuman/gitea-release-action. - Attaches firmware UF2 + Linux bundle (.deb / .AppImage / .rpm globs). - Uses secrets.GITHUB_TOKEN which the Forgejo runner injects. - Mac / Windows globs will be added back when those workers come online.act v6.4.0 was bailing at workflow-prepare with "'runs-on' key not defined in Build artifacts/desktop" when the release job's needs: [firmware, desktop] tried to resolve upstream runs-on. The matrix expression "runs-on: ${{ matrix.os }}" could not be statically resolved at prepare time. Collapsed the desktop job to a plain ubuntu-latest single-job form since only Linux is active right now; reintroduce the matrix once macOS / Windows workers come online.act v6.4.0 keeps tripping at workflow-prepare time on cross-job needs: even after the runs-on cleanup, so the firmware build, desktop build, and release publishing now all live in one ubuntu-latest job with no needs: graph. - Replaced akkuman/gitea-release-action with a curl block that hits the Forgejo (Gitea-compatible) API directly: POST /api/v1/repos/.../releases, then a POST to /releases/{id}/assets for each file. - Release step gated on `if: startsWith(github.ref, 'refs/tags/v')` so regular pushes still build but skip publishing. - Artifacts (UF2 + Linux bundle) still upload via upload-artifact for the per-run Artifacts panel, separate from the release attach. - jq added to the apt install line for the JSON payload.