Earl Warren 98be7826a3 chore(dependency): pin redis to 7.2 for testing ... There is no need to pin a specific patch version for testing. The worst that can happen in this context is that the CI fails and it can be addressed in this context. It will not impact releases.		2024-05-25 08:25:51 +02:00
..
backport.yml	[CI] configure backport to comment on the PR on failure	2024-04-15 18:23:57 +02:00
build-release-integration.yml	Disable duplicate builds	2024-03-25 13:24:53 +01:00
build-release.yml	fix(release): add missing ARG RELEASE_VERSION	2024-04-17 17:16:53 +02:00
cascade-setup-end-to-end.yml	[CI] simplify end-to-end test cascading PR	2024-03-20 18:16:56 +01:00
e2e.yml	Revert "[CI] pin go v1.22.2 version"	2024-04-05 05:31:00 +02:00
mirror.yml	[CI] mirror to forgejo-integration daily instead of each commit	2024-02-17 11:55:52 +01:00
publish-release.yml	Update forgejo/forgejo-build-publish action to v5	2024-04-12 10:19:15 +00:00
renovate.yml	Update ghcr.io/visualon/renovate Docker tag to v37.374.3	2024-05-22 20:06:04 +00:00
testing.yml	chore(dependency): pin redis to 7.2 for testing	2024-05-25 08:25:51 +02:00