• 1.0.6 a4792a7a83

    1.0.6
    All checks were successful
    Dotnet build and test / log-the-inputs (pull_request) Successful in 46s
    Dotnet build and test / build (pull_request) Successful in 12m18s
    Forgejo Release / release (push) Successful in 6m34s
    Stable

    notazof released this 2026-08-17 05:44:12 +01:00 | 91 commits to main since this release

    Added

    • Self-hosted Forgejo Actions runner now drives the CI build for the
      yavsc repository, using the
      pazof/yavsc-build-env:debian12-dotnet10-android36-v2 image pulled
      from Docker Hub. Workflow runs end-to-end: clone, restore, build,
      test, with NuGet.config picking up the isn.pschneider.fr feed.
    • 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-rolled sed-based extractor that was matching the
      wrong id field on minified responses.

    Changed

    • CI workflow .forgejo/workflows/buildAndTest.yml no 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

    • Dockerfile and Dockerfile.backend no longer carry a redundant
      dotnet nuget add source step that conflicted with the GitHub
      Actions APK build (--allow-insecure-connections on an HTTPS
      endpoint, exit 1). NuGet.config at the repo root supplies the
      isn.pschneider.fr feed for every restore, including inside Docker.
    • .forgejo/workflows/release.yml: PATCH on /releases/{id} no longer
      404s on existing releases. The previous sed-based json_field
      matched the last id on 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 to jq for both body construction and
      field extraction.
    Downloads