Lightning Piggy: correct publisher to "The Lightning Piggy Project"

[bitcoin3us]

The Lightning Piggy entry in app_index.json lists the publisher as "LightningPiggy Foundation", which is not the correct name of the project. Changed to "The Lightning Piggy Project".

The AppStore app reads this field for the listing and renders it as the app's developer/publisher (appstore.py passes app["publisher"] into App, and app_detail.py shows it), so the store was displaying the wrong name.

Publisher string only: version and download_url are deliberately left at 0.7.2 so the existing .mpk keeps resolving.

Companion PR fixing the same field at the source (the app's own MANIFEST.JSON, so future publishes carry the correct name): LightningPiggy/LightningPiggyApp#51

Note: the BadgeHub.eu listing (now the AppStore's default backend) carries the same name in app_metadata.author, which app_detail.py maps to the displayed publisher. That is outside this repo and needs a re-publish or listing edit to fully match.

🤖 Generated with Claude Code

[ThomasFarstrike]

Does this still make sense, now that apps.MicroPythonOS.com won't be used anymore? Thanks!

[bitcoin3us]

This edits app_index.json, i.e. the retired apps.micropythonos.com store index, so it's moot here — closing. The metadata now lives on BadgeHub: the Lightning Piggy project page there currently ships publisher "LightningPiggy Foundation" (that's what a fresh install's MANIFEST.JSON says), so if the rename to "The Lightning Piggy Project" is still wanted, it belongs in the BadgeHub project metadata rather than in this repo.

[ThomasFarstrike]

OK I updated it at https://badgehub.eu/page/project/com.lightningpiggy.displaywallet too!

[bitcoin3us]

Following up here since this is where the publisher question came up: the rename is important to us — it should be "The Lightning Piggy Project", not "Foundation". The app's manifest already has it (LightningPiggyApp master, version 0.7.3), and BadgeHub derives its author field from the manifest inside the uploaded .mpk — so the only stale copy is the BadgeHub listing, still at the 0.7.2 package from Aug 15.

I've cut the release: https://github.com/LightningPiggy/LightningPiggyApp/releases/tag/0.7.3 — .mpk attached: https://github.com/LightningPiggy/LightningPiggyApp/releases/download/0.7.3/com.lightningpiggy.displaywallet_0.7.3.mpk (built per the bundling guide; also includes the hero-density and NWC-error-surfacing changes merged since 0.7.2).

The BadgeHub project com.lightningpiggy.displaywallet is owned by your BadgeHub account (the one holding the com.micropythonos.* apps), so I can't upload it. Could you either upload this .mpk as the new release there, or — probably better long-term, since I'm the maintainer of the app repo — transfer the BadgeHub project to my account (the one that owns org.zaptv.blocktv) so future releases are self-serve? Thanks!

[ThomasFarstrike]

The BadgeHub project com.lightningpiggy.displaywallet is owned by your BadgeHub account (the one holding the com.micropythonos.* apps), so I can't upload it. Could you either upload this .mpk as the new release there

Indeed, forgot about that. Done!

transfer the BadgeHub project to my account (the one that owns org.zaptv.blocktv) so future releases are self-serve

That's also my preferred option! I don't see a way to do that myself on BadgeHub.eu so I'll ask the maintainer if they can do that for us :-)

[bitcoin3us]

Confirmed via the API: revision 65, author now "The Lightning Piggy Project" — thank you! And great that the ownership transfer is your preference too; whatever the BadgeHub maintainer needs from my side (the account is the one owning org.zaptv.blocktv), just say.