restore previous fixes with renamed token property
Build / build-and-push (push) Failing after 8s

This commit is contained in:
2026-09-05 13:48:18 +01:00
parent a3b44907b8
commit 923d68f317
2 changed files with 18 additions and 14 deletions
+9 -7
View File
@@ -10,18 +10,18 @@ name: Build
# This project's CI/CD scope is intentionally just test/build/push -- # This project's CI/CD scope is intentionally just test/build/push --
# deployment is being split into a separate project. # deployment is being split into a separate project.
# #
# Requires secrets.GITEA_TOKEN (auto-injected by Gitea Actions; needs the # Requires secrets.BUILD_API_TOKEN -- a personal access token
# "packages" permission scope to push images). # (write:package scope) from the pushing account, stored manually as a repo
# secret. The auto-injected secrets.GITEA_TOKEN does NOT work for this: it
# never grants package-registry access regardless of the workflow's own
# `permissions:` block -- a known Gitea limitation, not a config mistake
# (https://github.com/go-gitea/gitea/issues/23642).
on: on:
push: push:
branches: [main] branches: [main]
workflow_dispatch: workflow_dispatch:
permissions:
contents: read
packages: write
jobs: jobs:
build-and-push: build-and-push:
runs-on: ubuntu-latest runs-on: ubuntu-latest
@@ -41,7 +41,9 @@ jobs:
- uses: actions/checkout@v4 - uses: actions/checkout@v4
- name: Log in to the container registry - name: Log in to the container registry
run: echo "${{ secrets.GITEA_TOKEN }}" | docker login code.aneur.in -u "${{ gitea.actor }}" --password-stdin env:
BUILD_API_TOKEN: ${{ secrets.BUILD_API_TOKEN }}
run: echo "$BUILD_API_TOKEN" | docker login code.aneur.in -u "${{ gitea.actor }}" --password-stdin
- name: Promote the current "latest" to "previous" - name: Promote the current "latest" to "previous"
run: | run: |
+9 -7
View File
@@ -10,17 +10,17 @@ name: Release
# Assumes tags are cut from commits already on main (and so already covered # Assumes tags are cut from commits already on main (and so already covered
# by ci.yml's checks) -- this workflow doesn't run the test suite itself. # by ci.yml's checks) -- this workflow doesn't run the test suite itself.
# #
# Requires secrets.GITEA_TOKEN (auto-injected; needs the "packages" # Requires secrets.BUILD_API_TOKEN -- a personal access token
# permission scope to push images). # (write:package scope) from the pushing account, stored manually as a repo
# secret. The auto-injected secrets.GITEA_TOKEN does NOT work for this: it
# never grants package-registry access regardless of the workflow's own
# `permissions:` block -- a known Gitea limitation, not a config mistake
# (https://github.com/go-gitea/gitea/issues/23642).
on: on:
push: push:
tags: ['*'] tags: ['*']
permissions:
contents: read
packages: write
jobs: jobs:
build-and-push: build-and-push:
runs-on: ubuntu-latest runs-on: ubuntu-latest
@@ -39,7 +39,9 @@ jobs:
- uses: actions/checkout@v4 - uses: actions/checkout@v4
- name: Log in to the container registry - name: Log in to the container registry
run: echo "${{ secrets.GITEA_TOKEN }}" | docker login code.aneur.in -u "${{ gitea.actor }}" --password-stdin env:
BUILD_API_TOKEN: ${{ secrets.BUILD_API_TOKEN }}
run: echo "$BUILD_API_TOKEN" | docker login code.aneur.in -u "${{ gitea.actor }}" --password-stdin
- name: Build and push the image - name: Build and push the image
run: | run: |