[Proposal] automatic publish into platfromio registry

[sebastian-toepfer]

The OpenOCD version in the PlatformIO registry is very old and lacks many features. Why don't we publish every release there? If you think that's a good idea, I have a workflow that should make that possible. The problem with my version is that the package is published under my username, which wouldn't be right given all the great work you've done.

I'm not entirely sure if we can use the release trigger, since the artifacts apparently aren't added until later. But why don't we just start with a different workflow based on Dispatch?

@ilg-ul: what do you think?

[ilg-ul]

Any suggestions to improve the xPack project are highly appreciated!

I took a look at your workflow, but I'm not familiar with PlatformIO and probably I missed some details.

It looks like you are downloading the xPack OpenOCD binaries from the GitHub Releases, repack them and publish them on PlatformIO.

Is this correct?

[sebastian-toepfer]

yes it download the assets generate a package.json and publish it to the platformio registry. then it is usable with platformio and can be reference by other packages. and this is for OpenOCD the case for the stm32platfrom.

[ilg-ul]

I see. Very nice, glad to hear that my project is useful for PlatformIO.

What exactly do you suggest?

I have no experience with PlatformIO and no connections with the team managing it, so no rights to publish anything on their registry, therefore I'm not sure how I can be of any help.

[sebastian-toepfer]

publish is easy :) you only need an account, is free and you can publish public packages. do you think is a way? than you must only put the pat as ghsecret.

I'm only a platformio user with limited knowledge. but it helps me a lot to start my journey with embedded software development. and until my issues with stm32 boards i never had known that OpenOCD exists.

[ilg-ul]

I don't know what would be the best way forward. :-(

I'd appreciate some advice from the PlatformIO community, and I'd also try to avoid suggesting them solutions that they do not really need.

Then, personally I'm not that fond of having to maintain repackaged xPack binaries. Why not use them as they are?