ci: re-declare packages: write for forward compat with gitea#39070
Provision Coder Templates / build-images (push) Successful in 14s
Provision Coder Templates / provision (push) Successful in 1m50s

Currently a no-op given GITEA_TOKEN can't reach the registry at all yet,
but harmless to have in place now so nothing needs to change here once
that fix ships and PACKAGE_REGISTRY_TOKEN can eventually be retired.
This commit is contained in:
2026-08-27 09:21:15 +02:00
parent 757a94557b
commit c64987a840
+6
View File
@@ -59,6 +59,12 @@ jobs:
# container.volumes mount for the same path here fails at container # container.volumes mount for the same path here fails at container
# creation with "Duplicate mount point: /var/run/docker.sock". # creation with "Duplicate mount point: /var/run/docker.sock".
runs-on: docker-build runs-on: docker-build
# Currently a no-op (see the PACKAGE_REGISTRY_TOKEN note above) but
# harmless to declare now - once go-gitea/gitea#39070 ships, GITEA_TOKEN
# will need this to get package write access, so this is one less thing
# to remember when PACKAGE_REGISTRY_TOKEN can eventually be retired.
permissions:
packages: write
outputs: outputs:
failed_templates: ${{ steps.build.outputs.failed_templates }} failed_templates: ${{ steps.build.outputs.failed_templates }}
# docker:27-cli (Alpine) has no bash - only the POSIX /bin/sh (busybox # docker:27-cli (Alpine) has no bash - only the POSIX /bin/sh (busybox