gitlab-runner v19.3.1 released: review CRD and behaviour

[github-actions]

Upstream released v19.3.1; DefaultRunnerImage pins v19.3.0.

• Release notes
• CHANGELOG
• Runner image: gitlab/gitlab-runner:alpine-v19.3.1

Executor config

Upstream Kubernetes executor toml keys, v19.3.0 to v19.3.1. Compared as (struct, key) pairs rather than bare key names: 253 upstream, 241 here. The exposure check runs in both directions, with 14 of them excluded by hack/runner-release-watch.suppress. Outside the Kubernetes executor subtree: 0 added, 0 removed.

No keys added to the Kubernetes executor config

No new CRD fields needed for the executor config.

Every upstream Kubernetes executor key is exposed

No (struct, key) pair in the v19.3.1 Kubernetes executor config is missing from api/v1beta2/gitlab_types.go.

Helper image

Helper image published for v19.3.1 (69 tags). Linux flavours:

• (default)
• alpine-edge
• alpine-latest
• alpine3.21
• concrete
• ubi-fips
• ubuntu

Before closing

• Decide whether any added key needs a CRD field in api/v1beta2.
• Check the release notes for behaviour changes the reconciler assumes.
• Bump DefaultRunnerImage and let e2e exercise the new runner.