5 Commits

Include renames

Author	SHA1	Message	Date
zwitschi	afd086ba11	Fail loudly when release uploads do not land ... Follow-up to the publishing fix: CI created the v0.2.11 release and logged each upload, but the assets never arrived, so the job looked successful while the release was empty. The host root filesystem is full (7.8G, 100%), and Gitea answered HTTP 500 "Attachments.Save: no space left on device". - publish_release.sh now checks the HTTP status of every asset upload and prints the response body on failure, then verifies the release reports as many assets as were sent. Empty releases can no longer pass silently. - Deleted the empty v0.2.11 release so the "latest" release (v0.2.10) still has all five artifacts; the tag itself remains. - TODO/MEMORY record the host disk blocker with concrete cleanup commands and note that v0.2.11 artifacts are built locally in build/ for upload once space exists.	2026-10-31 21:38:12 +01:00
zwitschi	b4d189c325	Publish releases with the runner's checkout credentials ... The v0.2.10 tag build still failed to publish: its env dump showed no token at all, because this Gitea/act runner does not provide `github.token`, and the repo has no GITEA_TOKEN secret. publish_release.sh now resolves credentials in order: GITEA_TOKEN, GITEA_AUTH_HEADER, ~/.git-credentials, then the local git extraheader that actions/checkout writes for the job. That header carries the runner's basic-auth credentials for the same server, so tag builds publish with no repo secret. Verified by adding the extraheader locally and publishing v0.2.10 (all five artifacts: Linux/Windows/macOS ports, NSIS installer, AppImage), then removing it. Docs: RELEASING describes the four credential sources and warns that github.token is not available here; MEMORY records both failed attempts and the final fix; TODO keeps the "verify on the next tag" follow-up. Version 0.2.11.	2026-10-31 21:30:24 +01:00
zwitschi	6684d36739	Fix release publishing and add a CI token fallback ... Tag builds since v0.2.2 built all artifacts but never published a release: - tools/publish_release.sh only assembled AUTH in the GITEA_TOKEN branch; the ~/.git-credentials branch set CRED and then used an unbound ${AUTH[@]} under `set -u`, so every API call failed and the job ended "could not create or find release". It now sets AUTH=(-u "$CRED"). - The repo has no GITEA_TOKEN secret and the runner has no git credentials, so the workflow now falls back to the built-in workflow token: GITEA_TOKEN: ${{ secrets.GITEA_TOKEN || github.token }}. v0.2.9 was then built and published locally with all five artifacts (portable Linux/Windows/macOS, NSIS installer, AppImage) and the release page verified via the API. v0.2.4-v0.2.8 remain unpublished; they are superseded by the latest. Docs - docs/RELEASING.md records the incident and the local-publish fallback. - TODO gains a release-pipeline follow-up (verify CI on the next tag). - MEMORY notes the root cause, the missing secret, and which releases exist. - Version 0.2.10.	2026-10-31 21:23:09 +01:00
zwitschi	f2d218cc27	Fix publish_release.sh to upload installer + AppImage; document host REQUIRE_SIGNIN_VIEW ... - Script uploaded only the three portable binaries; v0.2.1 release was missing step-line-setup-0.2.1.exe and the AppImage. Now uploads the full set (extras when present), reuses existing releases (adds missing assets), and falls back to ~/.git-credentials basic auth when GITEA_TOKEN is unset - Back-filled both missing assets onto the live v0.2.1 release via API (release now carries all 5 artifacts) - TODO/RELEASING/MEMORY document the findings and the host admin steps for anonymous downloads ([service] REQUIRE_SIGNIN_VIEW)	2026-10-31 14:37:56 +01:00
zwitschi	191377fae2	Prepare first downloadable release: install export templates, build 0.1.0 binaries, add publish helper ... - Install Godot 4.3 export templates locally and fix macOS export (enable rendering/textures/vram_compression/import_etc2_astc) - Build Linux/Windows/macOS artifacts into build/ via tools/build_releases.sh; Linux binary passes headless smoke test - Add tools/publish_release.sh (creates Gitea release + uploads assets with a token) - TODO: mark build/install steps done; publishing v0.1.0 + link verification remain as the single action blocker (needs GITEA_TOKEN)	2026-10-31 12:57:20 +01:00