Platform package tried to publish is not visible

Registry
1

@ivankravets

I published a development platform package a few days ago and can’t determine whether it was accepted. I’d like to confirm the status before taking any further action.

  • Owner (organization): lee-lab-skku
  • Owner of the organization: me (mirinae)
  • Package: arduinoq
  • Version: 1.0.0-rc.2
  • Type: platform
  • PlatformIO Core: 6.1.19

The organization’s representative email is set to the PI’s address, and that address does not have a PlatformIO account associated with it (mentioning just in case)

I’ve checked:

  • No confirmation email received
  • pio pkg search returns no matching package
  • The registry web dashboard shows no entry for it
  • pio access list returns nothing, both with and without the behalf of org.

The CLI appeared to complete without an error at publish time and insisted that the confirmation e-mail would be sent.

Is there a pending approval step, and if so, is there any way for a publisher to see that a submission is queued? Any guidance on how to proceed would be appreciated.

Regards

Edited: platform-arduinoq was the repository name, not the package name.

2

Could you share the link to the dev-platform?

3

The package likely awaits registry-side confirmation.

4

If you mean the repository: lee-lab-skku/platform-arduinoq

5

@ivankravets
Reminder: Could you please review and approve the package, or comment back which publication stage is wrong?

Thanks in advance.

ps. Would this confirmation step be applied every version bumps?

6

Sorry for the delay. The platform didn’t pass the automatic review and was flagged for manual review because the packages mentioned in the manifest are not listed in the registry (this is OK). It is now approved. Thanks!

7

Thanks a lot!
Related question: For that non registered packages, actually they are overriden by platform.py. This works well when the platform installation was triggered as a dependency declaration of the project configuration. However, trying a standalone installation via pio pkg install command seems not to call configure_default_packages so that it fails. Is this an intended behavior? (This issue doesn’t apply to the latest version of my platform, so it’s fine anyway)