Skip to content

Fail the build when the Akaunting release tag cannot be resolved - #124

Merged
cuneytsenturk merged 1 commit into
masterfrom
fix-release-tag
Nov 7, 2026
Merged

cuneytsenturk merged 1 commit into
masterfrom
fix-release-tag

Conversation

@cuneytsenturk

Copy link
Copy Markdown
Member

The scheduled run on 2026-11-01 failed for the main image. The anonymous GitHub API request for the latest Akaunting release was rate limited, and jq -r turned the error response into the string "null". The image was then tagged as nullakaunting/akaunting:latest and the push was denied, so latest, 3, 3.3 and 3.3.0 were never published.

Authenticate the request with the workflow token, retry it on transient errors, and stop the job when the response has no tag or the tag is not a plain x.y.z version, instead of pushing to a wrong tag.

The scheduled run on 2026-11-01 failed for the main image. The anonymous
GitHub API request for the latest Akaunting release was rate limited, and
`jq -r` turned the error response into the string "null". The image was
then tagged as `nullakaunting/akaunting:latest` and the push was denied,
so `latest`, `3`, `3.3` and `3.3.0` were never published.

Authenticate the request with the workflow token, retry it on transient
errors, and stop the job when the response has no tag or the tag is not
a plain x.y.z version, instead of pushing to a wrong tag.
@cuneytsenturk
cuneytsenturk merged commit 20243f6 into master Nov 7, 2026
0 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant