loading up the forgejo repo on tangled to test page performance
Merge pull request 'chore(ci): notify the k8s cluster about experimental releases' (#5747) from earl-warren/forgejo:wip-release-next-sync into forgejo
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5747
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
+8
+8
.forgejo/workflows/publish-release.yml
+8
.forgejo/workflows/publish-release.yml
···
70
70
# https://forgejo.org/docs/next/developer/infrastructure
71
71
curl -o /dev/null -sS https://v$major.next.forgejo.org/.well-known/wakeup-on-logs/forgejo-v$major
72
72
73
+
- name: upgrade v*.next.forgejo.org (k8s)
74
+
uses: https://code.forgejo.org/infrastructure/next-digest@v1.0.0
75
+
with:
76
+
url: https://placeholder:${{ secrets.TOKEN_NEXT_DIGEST }}@code.forgejo.org/infrastructure/next-digest
77
+
ref_name: '${{ github.ref_name }}'
78
+
image: 'codeberg.org/forgejo-experimental/forgejo'
79
+
image_suffix: '-rootless'
80
+
73
81
- name: set up go for the DNS update below
74
82
if: vars.ROLE == 'forgejo-experimental' && secrets.OVH_APP_KEY != ''
75
83
uses: https://code.forgejo.org/actions/setup-go@v5