The linting checks in the CI workflow currently is a step in a job that also builds a container image. But the linting step is only included when building for one architecture, not both. So, if the linting fails, that might cause unexpected pushing of only half of the multi-platform digests needed to build the final multi-platform container. This will break the existing latest image stored in ghcr.io. We need to move the linting check to its own CI job.
The linting checks in the CI workflow currently is a step in a job that also builds a container image. But the linting step is only included when building for one architecture, not both. So, if the linting fails, that might cause unexpected pushing of only half of the multi-platform digests needed to build the final multi-platform container. This will break the existing
latestimage stored in ghcr.io. We need to move the linting check to its own CI job.