Creating an API Key Role for Buildkite results in an access policy that requires Github Actions

[yob]

I work for Buildkite, and have been experimenting with using an API Key Role for publishing a personal gem from CI (pdf-reader).

Clicking the link from the gem page (https://rubygems.org/profile/oidc/api_key_roles/new?rubygem=pdf-reader&scopes%5B%5D=push_rubygem), I was able to create an API Key Role from the gem page (starts with rg_oidc_akr_meof, now revoked), however after clicking the Create Api Key Role button and the page reloading, the policy has a principal for Github Actions:

To fix it I can edit the token, then make a hidden form element visible and type in the Buildkite issuer:

Then, clicking the Update Api Key Role button saves the correct value:

Environment

Browser and its version: Firefox 133.0.3, Linux