cicd fixes and desktop fix
docker / image (push) Failing after 5s
lint / ruff (push) Successful in 40s
tests / desktop (push) Successful in 20s
tests / web (push) Successful in 33s
tests / android-core (push) Successful in 39s
tests / backend (push) Successful in 6m52s
android / apk (push) Successful in 4m51s

This commit is contained in:
timka123 committed 2026-10-22 19:08:07 +03:00
1 parent ea1ff48b97
commit 8c260feb78
4 files changed
+14 -4

No files matched your search

+1 -1
View File
@@ -96,7 +96,7 @@ jobs:
fi
fi
- uses: actions/upload-artifact@v4
- uses: actions/upload-artifact@v3
with:
name: kadence-release-apk
path: android/app/build/outputs/apk/release/app-release.apk
+12 -1
View File
@@ -15,6 +15,14 @@ on:
branches: [master]
tags: ["v*"]
# The built-in job token is enough to push to this instance's own registry; a
# REGISTRY_TOKEN secret is only needed when it is not (an older Gitea, or a
# restricted default permission mode). Ask for packages: write explicitly so the
# token is not silently read-only on instances that default to restricted.
permissions:
contents: read
packages: write
env:
REGISTRY: git.timka.su
IMAGE: git.timka.su/timka123/kadence
@@ -35,7 +43,10 @@ jobs:
# so a missing REGISTRY_USER secret does not fail the job with docker's
# unhelpful "username is empty".
REGISTRY_USER: ${{ secrets.REGISTRY_USER || github.repository_owner }}
REGISTRY_TOKEN: ${{ secrets.REGISTRY_TOKEN }}
# Gitea gives every job a built-in token (secrets.GITEA_TOKEN). Prefer
# an explicit secret, but fall back to that token so a fresh repository
# publishes without anyone having to mint one by hand.
REGISTRY_TOKEN: ${{ secrets.REGISTRY_TOKEN || secrets.GITEA_TOKEN }}
run: |
if [ -z "$REGISTRY_USER" ] || [ -z "$REGISTRY_TOKEN" ]; then
echo "::error::Container registry credentials are missing. Set REGISTRY_TOKEN (a token with package:write) under Settings → Actions → Secrets; REGISTRY_USER is optional and defaults to the repository owner."