It’s great that there are repo level CircleCI API tokens that are not associated with an individual user now.
However, if I create a project / repo level admin token, and try to use it to publish an orb, I get this error in the CI run:
Once an orb is created it cannot be deleted. Orbs are semver compliant, and each published version is immutable. Publicly released orbs are potential dependencies for other projects.
Therefore, allowing orb deletion would make users susceptible to unexpected loss of functionality.
Error: AUTHORIZATION_FAILURE
Exited with code exit status 255
I’m guessing this is a known / intended limitation (since orb publishing is restricted to orb admins, and / or since orbs technically aren’t associated with the “project”)? While one could create a GitHub bot user and use that for publishing, it would be nice if it were possible to publish an orb with a token not associated with a human.