Orb version 7.2.0 and 7.3.0 have not been published 😱

[fotos]

Orb version

7.2.0 and 7.3.0

What happened

The versions are missing from the orb registry. The latest published version is 7.1.1.

Additionally the last 2 releases are missing from GitHub releases.

The CircleCI pipeline failed with an error:

[9:55:24 AM] [semantic-release] › ✖  Failed step "publish" of plugin "semantic-release-circleci-orb"
[9:55:24 AM] [semantic-release] › ✖  An error occurred while running semantic-release: Error: Command failed: /home/circleci/circleci orb publish packed-orb.yml react-native-community/react-native@7.2.0 --token [secure]
Error: AUTHORIZATION_FAILURE

Looks like the token is incorrect. A long time has passed since the last time the orb was published and I'm suspecting the token has been removed due to the CircleCI security incident back in December 2022 / January 2023.

This probably requires manually (re-)running the CI steps to publish the orb and create the GH releases.

Expected behavior

I'd like to use version 7.2.0, which makes the detox setup optional, in our project.

[fotos]

cc: @cortinico and @devnev who merged the last couple of PRs. 🙏

[cortinico]

I don't have rights to publish this orb, maybe @devnev has

[devnev]

Nope, I'm just a contributor. @matt-oakes seems to have set it up originally?

[fotos]

Hi @matt-oakes! 👋

Is there anything I can do to help publish the missing orbs? Perhaps you can share the access with other maintainers to get this going?

I'm trying to take advantage of the change introduced in this PR #168 but it seems that it's only available in 7.3.0, which per this issue is not released.

@matt-oakes @devnev @cortinico if you could escalate to the right person to get this fixed it would be greatly appreciated 🙏

[cortinico]

I've sent an email to @matt-oakes as I believe he has the access to the orb publishing

[fotos]

Thank you @cortinico! 🙏

Any update here? If @matt-oakes can't be brought in to fix the issue, what else can be done?

For now, I'm working around my issue by pulling in the android docker image with my desired version manually without the rn/linux_android executor. It's a fine solution, but would still be nice to use what this orb provides.

Thanks 🙏

[matt-oakes]

Apologies for the lack of reply here. I don't routinely monitor this repo anymore as I don't use Circle CI.

I have replied to @cortinico's email and given them admin access to this repo. Additionally, there are already over 100 people with write access to this repo through the "react-native-community" members list.

It's not clear to me how to grant permission to publish on Circle CI, but @cortinico thinks that write/admin access to this Github repo will be enough. If it's not, then let me know and I can make the changes needed.

Again, apologies for the lack of reply.

[fotos]

Thank you @matt-oakes. I believe admin access is required in order to access the "Security" section, in the "Settings" tab, and rotate (recreate) the CircleCI deploy keys.

@cortinico let me know if you need help with anything. For example, I believe, to re-publish the currently unpublished releases, we need to remove the current tags , and re-trigger the CI/CD that will create the GH release and publish the orbs.

[cortinico]

@cortinico let me know if you need help with anything. For example, I believe, to re-publish the currently unpublished releases, we need to remove the current tags , and re-trigger the CI/CD that will create the GH release and publish the orbs.

@fotos Would you be up for fixing the Orb Development kit I started doing here?

• Update the Orb development kit #177

There should be some lint issues to fix and so on. Just send a similar PR and once the PR is green we can merge it and release a new version.

[fotos]

@cortinico sure, I can try.

I see that you did something similar to circle orb init in the repo. I think I can take it from here.