Jean-Luc Makiola
36beb2d0ad
The Codeberg publish has never once succeeded — 0.2.1, 0.2.2, 0.3.0, 0.3.1 and 0.3.2 all failed, and 0.3.0 was published by hand. Neither previous fix could have worked, because the cause isn't in this file: ref writes to jlmakiola/agendula on Codeberg fail. A tag push returns "cannot lock references" and POST /tags returns an empty-bodied 500, while the identical calls succeed on jlmakiola/calendula with the same token. Creating a release mints a tag, so it inherited the same failure. Attaching a release to a tag that is ALREADY there needs no ref write and returns 201. So split the responsibility the way it should have been: the push mirror owns delivering the tag, this step only attaches to it. Poll for the tag, then POST with no target_commitish so the API attaches rather than resolves a commit and mints one. If the tag never lands, fail with a pointer at the mirror instead of trying to create it. Drop continue-on-error. It reported green across five releases that never published, which is how 0.3.1's crash fix reached F-Droid while the Codeberg and Obtainium users who hit the crash got nothing. Tested against the live API before committing (unlike its predecessors): tag-present attaches 201, tag-absent exits 1 with the diagnostic. Note this does not by itself restore publishing — the mirror cannot write the v0.3.2 tag either, so Codeberg must repair the repo's ref store first. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2 lines
334 B
JSON
2 lines
334 B
JSON
{"tag_name": "v0.3.1", "name": "v0.3.1", "body": "### Fixed\n- Agendula no longer crashes on launch. Every 0.3.0 install was affected: the\n release build stripped a constructor that the background-work scheduler needs\n to open its database, and that happens before the app draws anything.\n\n", "draft": true, "prerelease": true}
|