Updating the [release notes GitHub pages](https://cri-o.github.io/cri-o)
can lead into merge conflicts if multiple jobs run on a
single branch in parallel (for example for merge commits and tags). We
do not consider this as fatal error any more, because we need the
release notes output for the next CI steps.

Failure ref: https://github.com/cri-o/cri-o/actions/runs/9350292608/job/25733441349#step:5:271

Signed-off-by: Sascha Grunert <[email protected]>

…8247-to-release-1.30

[release-1.30] Don't fail CI on GitHub pages push

Skip the first commit to avoid issues like:
#8249

Signed-off-by: Sascha Grunert <[email protected]>

…8273-to-release-1.30

[release-1.30] release-notes: Skip first commit

Signed-off-by: Peter Hunt <[email protected]>

The kubelet isn't going to try again to start a container, instead opting to recreate it.
Thus, this container will get leaked (until the pod cgroup is deleted)

This has impacts in disabling cpu load balancing on v2, as the container cgroup sticking around
means the target cpus are in use, breaking the kernel's exclusivity rule

Signed-off-by: Peter Hunt <[email protected]>

…8288-to-release-1.30

[release-1.30] server: clean up container after it failed to start

Signed-off-by: roman-kiselenko <[email protected]>

[release-1.30] Reload config should remove pinned images when an empty list is provided

Signed-off-by: Kubernetes Release Robot <[email protected]>

Bump version to 1.30.3