fix: refine watch detail layouts and automate RePebble publishing #23

• 
  @github-anthodev opened this merge request · Sep 13, 2026

  Summary

  Prepare Lapin Futé 1.0.1 with balanced departure detail layouts on Emery
  and Gabbro, refreshed Store screenshots, and automated RePebble publication.

  Watch UI

  • Balance header and countdown spacing on the departure detail screen.
  • Correct separator framing on Emery and refine vertical spacing on Gabbro.
  • Refresh the departure screenshots for both platforms.

  Release pipeline

  • Use version tags as GitHub release titles.
  • Add a separate RePebble Store job after successful GitHub release publication.
  • Reuse the exact validated PBW artifact and GitHub release notes without rebuilding.
  • Obtain a fresh Firebase ID token from an environment-scoped refresh token.
  • Validate artifact checksums, app identity, version, target platforms, and account ownership before uploading.
  • Reject versions that are not newer than those published for Emery and Gabbro.
  • Publish without automatic retries or screenshot replacement.

  Metadata and documentation

  • Bump all workspace versions and configuration-page About text to 1.0.1.
  • Add the MIT license and corresponding package metadata.
  • Simplify README badges and update the RePebble version badge.
  • Document Store credentials, environment protections, and publication behavior.

  Verification

  • Full host suite: 267 tests passed.
  • Release build and watch-build verification passed for Emery and Gabbro.
  • Detail-screen layouts were visually checked in isolated emulators.
  • Executed the Store job commands offline with the real 1.0.1 PBW and simulated remote responses.
  • Confirmed that the multipart upload preserves the validated artifact byte for byte.
  • Verified that preview tags, branch pushes, and manual dispatches skip Store publication.
  • Independent security review completed with no findings.

  No live Firebase authentication or Store upload was performed during
  validation. Emulator checks do not constitute physical-device validation.

  Deployment considerations

  • The pebble-store environment requires the
    PEBBLE_FIREBASE_REFRESH_TOKEN secret.
  • Configure required reviewers, where supported, and a tag-only v*
    deployment rule before enabling production publication.
  • Store publication is immediate once the job runs; it does not create a draft.
  • Public version checks cannot detect hidden draft collisions. Inspect the
    Store dashboard before rerunning an upload whose outcome is uncertain.

  Closes #22

• 
  @github-gitguardian-bot-52d85c · Sep 13, 2026

  ⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

  Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

  GitGuardian id	GitGuardian status	Secret	Commit	Filename
  37235331	Triggered	Google API Key	516c86d3b5af616c235e7ba7f12a10e86930b9be	packages/config-page/test/publish-pebble-store.test.js	View secret
  37235331	Triggered	Google API Key	516c86d3b5af616c235e7ba7f12a10e86930b9be	scripts/publish-pebble-store.mjs	View secret

  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

  To avoid such incidents in the future consider

  • following these best practices for managing and storing secrets including API keys and other credentials
  • install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

  ---

  🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Sign in to comment.