Earl Warren 54c8ac3e39 vars.SKIP_END_TO_END optionally skip tests when building a release ... The end-to-end tests will always fail when more than one release is broken. When trying to fix one, the other will get in the way and vice versa. The only way to get out of this deadlock is to replace all broken releases but one by doing the following on forgejo-integration: * set SKIP_END_TO_END to true in the actions vars tab * pushing a commit to the corresponding branch, fixing the problem		2024-10-17 07:31:22 +02:00
..
backport.yml	Update actions/git-backporting action to v4.8.2	2024-10-08 00:02:57 +00:00
build-release-integration.yml	Update actions/checkout action to v4 (forgejo) (#5427)	2024-09-30 13:08:26 +00:00
build-release.yml	vars.SKIP_END_TO_END optionally skip tests when building a release	2024-10-17 07:31:22 +02:00
cascade-setup-end-to-end.yml	ci: use mirror or bitnami images	2024-08-14 12:10:53 +02:00
forgejo-integration-cleanup.yml	chore(ci): do not remove tags from forgejo-integration	2024-08-11 07:22:21 +02:00
mirror.yml	chore(ci): Use mirrored container images for node	2024-08-12 16:11:35 +02:00
publish-release.yml	Update actions/setup-go action to v5	2024-10-01 10:02:16 +00:00
release-notes-assistant-milestones.yml	Update actions/setup-go action to v5	2024-10-01 10:02:16 +00:00
release-notes-assistant.yml	Update actions/setup-go action to v5	2024-10-01 10:02:16 +00:00
renovate.yml	Update renovate to v38.121.0	2024-10-14 20:04:12 +00:00
testing.yml	chore(ci): update changed-files actions URL for consistency	2024-10-07 03:21:45 +02:00