Feature request: pebble publish — update listing metadata & replace screenshots on an existing app
Summary
pebble publish can only set listing metadata (description, name, category, icons) and screenshots when an app is first created. On every subsequent publish of an existing app, that metadata is ignored and screenshots are appended, never replaced. There is no CLI path to update a description or curate the screenshot set after creation — it can only be done in the web dashboard. This breaks a fully-CLI / CI publishing workflow.
Current behaviour (pebble-tool 5.0.37, SDK 4.9.169)
Re-publishing an existing app:
--description, --name, --category, --source, --icon-small, --icon-large are documented as "used when creating a new app" and are silently ignored for an app that already exists. So the store description stays frozen at whatever it was at creation.--screenshots FILE… uploads/appends — it does not replace the existing set. After two publishes with 5 screenshots each plus the originals, the listing showed 11 screenshots (old + new piled up), with no way to remove the stale ones from the CLI.--release-notes does update per release (this part works well).
Net effect: I can ship a new binary version from the CLI, but the listing's description and screenshots can only be fixed by hand in the dashboard.
Use case
I maintain a family of 7 watchfaces (one .pbw each) and publish all of them as visible betas on every iteration via a script (pebble publish --non-interactive --is-published …). Each iteration I regenerate fresh emulator screenshots and update the descriptions to document new settings. Today the binary + version + release-notes go out cleanly, but every iteration I then have to open 7 dashboard pages by hand to (a) paste the new description and (b) delete the now-stale screenshots. That manual step defeats the point of a scriptable publish.
Proposed
For an existing app, let pebble publish (and/or a dedicated pebble app update subcommand) honour:
- Listing metadata updates —
--description, --name, --category, --icon-small, --icon-large, --source applied to the existing app, not just on creation.
- Screenshot replacement — a
--replace-screenshots flag (or make --screenshots replace-by-default with --append-screenshots to opt into the current behaviour), so the uploaded set becomes the canonical set. Bonus: a way to clear/delete screenshots.
Even just #1 and #2 behind explicit flags would make a 100% CLI / CI publishing loop possible.
Environment
Feature request:
pebble publish— update listing metadata & replace screenshots on an existing appSummary
pebble publishcan only set listing metadata (description, name, category, icons) and screenshots when an app is first created. On every subsequent publish of an existing app, that metadata is ignored and screenshots are appended, never replaced. There is no CLI path to update a description or curate the screenshot set after creation — it can only be done in the web dashboard. This breaks a fully-CLI / CI publishing workflow.Current behaviour (pebble-tool 5.0.37, SDK 4.9.169)
Re-publishing an existing app:
--description,--name,--category,--source,--icon-small,--icon-largeare documented as "used when creating a new app" and are silently ignored for an app that already exists. So the store description stays frozen at whatever it was at creation.--screenshots FILE…uploads/appends — it does not replace the existing set. After two publishes with 5 screenshots each plus the originals, the listing showed 11 screenshots (old + new piled up), with no way to remove the stale ones from the CLI.--release-notesdoes update per release (this part works well).Net effect: I can ship a new binary version from the CLI, but the listing's description and screenshots can only be fixed by hand in the dashboard.
Use case
I maintain a family of 7 watchfaces (one
.pbweach) and publish all of them as visible betas on every iteration via a script (pebble publish --non-interactive --is-published …). Each iteration I regenerate fresh emulator screenshots and update the descriptions to document new settings. Today the binary + version + release-notes go out cleanly, but every iteration I then have to open 7 dashboard pages by hand to (a) paste the new description and (b) delete the now-stale screenshots. That manual step defeats the point of a scriptable publish.Proposed
For an existing app, let
pebble publish(and/or a dedicatedpebble app updatesubcommand) honour:--description,--name,--category,--icon-small,--icon-large,--sourceapplied to the existing app, not just on creation.--replace-screenshotsflag (or make--screenshotsreplace-by-default with--append-screenshotsto opt into the current behaviour), so the uploaded set becomes the canonical set. Bonus: a way to clear/delete screenshots.Even just #1 and #2 behind explicit flags would make a 100% CLI / CI publishing loop possible.
Environment