La section [1.0.6] - stable du CHANGELOG mentionnait encore debian12-dotnet10-android36-v1 et ne décrivait pas le fix du PATCH release qui tombait en 404 à cause du sed greedy + JSON minifié. Mets à jour avant de relancer la publication de la release 1.0.6 (workflow_dispatch), pour que le body publié reflète l'état réel de l'infra (image v2 avec jq) et du workflow.
2.3 KiB
2.3 KiB
Changelog
Toutes les modifications notables de PostIt et de la plateforme Yavsc sont documentées dans ce fichier.
Le format suit Keep a Changelog, et ce projet adhère au Semantic Versioning.
À noter : la parité du numéro de patch porte une signification de canal :
- patch pair (ex.
1.0.0,1.0.2) → stable - patch impair (ex.
1.0.1,1.0.3) → preview - suffixe (ex.
1.0.0-rc1,1.0.0-alpha) → instable
Cette convention est partagée avec le dépôt
postit-debian
pour la production des paquets .deb.
Unreleased
Added
Changed
Fixed
Removed
1.0.6 - stable
Added
- 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 onactions/checkout(the runner image has no Node); clones yavsc viagit, fetches the ref under test, and initializes submodules over HTTPS.
Fixed
DockerfileandDockerfile.backendno longer carry a redundantdotnet 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 theisn.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_fieldmatched 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.