-
1.0.6
Stablereleased this
2026-08-17 05:44:12 +01:00 | 91 commits to main since this releaseAdded
- Self-hosted Forgejo Actions runner now drives the CI build for the
yavsc repository, using the
pazof/yavsc-build-env:debian12-dotnet10-android36-v2image pulled
from Docker Hub. Workflow runs end-to-end: clone, restore, build,
test, with NuGet.config picking up theisn.pschneider.frfeed. - The build-env image now ships
jq(Debian package, ≥ 1.7), so the
release workflow can build JSON bodies and parse API responses
without a hand-rolledsed-based extractor that was matching the
wrongidfield on minified responses.
Changed
- CI workflow
.forgejo/workflows/buildAndTest.ymlno longer relies on
actions/checkout(the runner image has no Node); clones yavsc via
git, fetches the ref under test, and initializes submodules over
HTTPS.
Fixed
DockerfileandDockerfile.backendno longer carry a redundant
dotnet nuget add sourcestep that conflicted with the GitHub
Actions APK build (--allow-insecure-connectionson an HTTPS
endpoint, exit 1).NuGet.configat the repo root supplies the
isn.pschneider.frfeed for every restore, including inside Docker..forgejo/workflows/release.yml: PATCH on/releases/{id}no longer
404s on existing releases. The previoussed-basedjson_field
matched the lastidon the line (the author's), so it tried to
PATCH/releases/1(the first user of the instance) instead of the
actual release id. Switched tojqfor both body construction and
field extraction.
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download
- Self-hosted Forgejo Actions runner now drives the CI build for the