Jamie Magee

OpenTelemetry containers are also signed with cosign: ``` $ cosign verify \ docker.io/otel/opentelemetry-collector-contrib:latest \ --certificate-oidc-issuer https://token.actions.githubusercontent.com \ --certificate-identity https://github.com/open-telemetry/opentelemetry-collector-releases/.github /workflows/base-release.yaml@refs/tags/v0.99.0 Verification for index.docker.io/otel/opentelemetry-collector-contrib:latest -- The following checks were performed on...

Let me open a draft PR to show you what I'm thinking.

See #272

No, that's going to add too much complexity IMO. I'll have to do: | | Exists locally | Doesn't exist locally | |------------------------|---------------------------|-----------------------| | Exists remotely | Compare digest |...

OpenTelemetry containers are also signed with cosign: ``` $ cosign verify \ docker.io/otel/opentelemetry-collector-contrib:latest \ --certificate-oidc-issuer https://token.actions.githubusercontent.com \ --certificate-identity https://github.com/open-telemetry/opentelemetry-collector-releases/.github /workflows/base-release.yaml@refs/tags/v0.99.0 Verification for index.docker.io/otel/opentelemetry-collector-contrib:latest -- The following checks were performed on...

I emailed 8bitdo, asking if they would publish any new firmware versions and received this reponse: >Greetings. > >Thanks for the e-mail. I'm here to assist you. > >There are...

I am seeing the same issue [here](https://github.com/JamieMagee/aur-packages/runs/6720434301?check_suite_focus=true) It looks like it's failing to download `nodejs` version `18.1.0`, but the latest is currently `18.3.0`. I think the pacman databases need to...

Setting `aur: true` is a workaround, as paru is called with `-Syu` https://github.com/hapakaien/archlinux-package-action/blob/2d9dafa60e3349bbd1ad9ce4e27b71220377c637/entrypoint.sh#L59

Related to #9482 Test failures are due to Ubuntu 24.04 shipping with an `ubuntu` user with UID 1000 that conflicts with the one we try to create.

@dependabot rebase