Skip to content

chore(platforms): sync the catalogue snapshot with production - #1221

Merged
JamieRuderman merged 1 commit into
feat/permitteer-loginfrom
fix/platform-snapshot-sync
Sep 15, 2026
Merged

JamieRuderman merged 1 commit into
feat/permitteer-loginfrom
fix/platform-snapshot-sync

Conversation

@JamieRuderman

Copy link
Copy Markdown
Member

Follow-up to #1203 now that graphql-api#209 is deployed to production.

The committed snapshot was built offline from the seed before the API shipped. Regenerating it against the live catalogue (the real platformTypes + platformInstallations response from prod, run through the generator's own write path) shows types and routes identical and exactly two field differences: instructions on the android and docker-extension rows, added on the API side after the snapshot was cut.

  • android: "Install the Remote.It ScreenView app from the Play Store, open it, and enter this code to register the device."
  • docker-extension: "Install the Remote.It Jumpbox extension in Docker Desktop, open it, and enter this code to register."

Both are translated into ja/de/es in the platforms namespace rather than left empty.

No visible desktop change: both pages keep local JSX instructions, which win over the catalogue per the merge rule. The MCP create_registration_code tool does return these strings for code platforms, and the snapshot's contract is that platforms:check passes against production — it now does.

Verification: npm run platforms:check against the live response reports up to date; i18n:check passes (4 locales, 3 namespaces); typecheck clean.

@JamieRuderman
JamieRuderman merged commit 138bcb5 into feat/permitteer-login Sep 15, 2026
3 checks passed
@JamieRuderman
JamieRuderman deleted the fix/platform-snapshot-sync branch September 15, 2026 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant