Library is not updating in Platformio registry

Libraries
1

I am the authour of this arduino library PlatformIO Registry

The version in the Platform.io registry seems to be stuck at 0.0.1 even though the GitHub repo has the current tag of 0.1.8 and has been at this version for 3 days.

Is there anything I can do to get the Platformio registry updated to the latest version?

Thanks

2

Did you do a pio pkg publish for initially pushing the library to the PIO registry?

3

Thanks Max. This seems to be the issue. The library seems to have been picked up automatically from the Arduino library repo. It is published from the LNbits repo, I’m a contributor there GitHub - lnbits/arduino-nostr

I’ve now set myself up as the owner of the library, but when I try pio pkg publish --owner lnbits I get the error

Error: You do not have permission to publish a package using the lnbits account

and if I try to publish without the --owner flag it looks as though it will publish to blackcoffeexbt/Nostr rather than lnbits/Nostr

Warning! A package with the name `Nostr` is already published by the next owners: lnbits

Are you sure you want to publish the library blackcoffeexbt/Nostr@0.1.8 to the registry?

Any ideas what I can do to publish to lnbits/Nostr?

4

CC @ivankravets could you help out here with publishing?

1 Like
5

Could you provide an output of pio org list comamnd?

6

Thanks Ivan! Looks like I’m now in the lnbits org and have updated the lib.

Much appreciated :slight_smile:

1 Like
7

I am having a similar problem with my library.

I am the author of this arduino library PlatformIO Registry 5

Until recently when I released a new version it updated correctly in the Arduino IDE, and also automatically updated for PlatformIO.

Recently I messed up the tags and it took a couple of releases before I sorted that out. The Arduino library now correctly shows v1.1.17 but PlatformIO still shows v1.1.14

Is there anyway to correct this?

Thanks
peter

8

Yes, the PlatformIO crawler detected multiple conflicts (different versions in the multiple manifests). The crawler automatically tries to update the library with a special delay. The 1.1.17 is a valid version/tag and it was successfully added to the registry:

9

Much Appreciated

Peter