Skip to content
This repository was archived by the owner on Oct 27, 2026. It is now read-only.

refactor(integrations): stop relying on the coming-soon flag - #1251

Closed
samkujovich wants to merge 1 commit into
fix/integrations-index-from-public-catalogfrom
chore/drop-coming-soon
Closed

samkujovich wants to merge 1 commit into
fix/integrations-index-from-public-catalogfrom
chore/drop-coming-soon

Conversation

@samkujovich

@samkujovich samkujovich commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Part of GRO-615

What/why

Arcade no longer lists "coming soon" toolkits: ArcadeAI/monorepo#5732 deletes the 37 placeholders from design-system, and isComingSoon is false on every remaining toolkit. The field itself stays, because the public catalog returns it. Docs still has a whole coming-soon path (a "Notify me" modal, a card state, a sort rule) plus a generator that rejects branding without the field. This PR removes that path and stops docs from depending on the field. Readers see no change: after #1249 the index has no coming-soon cards.

Stacked on #1249. Independent of ArcadeAI/monorepo#5732; either can merge first.

Codebase changes

  • Generator: isComingSoon is removed from its schemas, merger, and freshness check. Zod drops unknown keys, so it accepts branding with or without the field.
  • Integrations index: a toolkit without a page is now dropped. Previously it rendered as a non-clickable "coming soon" card that opened a "Notify me" modal. With that gone, the modal and its context are deleted, and the resolver returns each card's link.
  • Still set: isComingSoon: false on the two partner toolkits, because the design-system Toolkit type requires it. Docs' own ToolkitWithDocsLink omits it, so nothing in docs reads it.

Proof

Behavior How it was proven
Generator keeps branding with or without isComingSoon Unit: new test in public-catalog-api.test.ts feeds branding that still carries the field; the existing fixtures, now without it, also pass
Index drops page-less toolkits and links every card Unit: rewritten resolveIndexToolkits tests in integration-index-links.test.ts; the live-data tests confirm every card links to an existing page
Index unchanged for readers Real: resolved the index from the repo's data on this branch and on #1249. Both have the same 125 cards
Nothing else regressed pnpm test (900 passed), pnpm lint, tsc --noEmit

Additional notes

  • The "Notify me" modal sent a PostHog Notify me clicked event with the visitor's email. That event stops, and Tool card clicked loses its is_coming_soon property, which was always false after fix(integrations): list the toolkits the public catalog publishes #1249.
  • Next nightly run: generated toolkit files drop their isComingSoon line, so the first generated PR after this merges touches every toolkit file by one line.

~ 🤖 sam-i-am, Sam’s Agent

Arcade is removing the coming-soon concept from the design-system
toolkit metadata. The design-system metadata feeds the public catalog,
and the docs generator required isComingSoon on every toolkit's
branding, so dropping the field upstream would have stripped branding
from every generated toolkit file.

- The generator no longer reads or writes isComingSoon. Zod strips
  unknown keys, so it accepts branding with or without the field.
- The integrations index drops toolkits without a page instead of
  rendering them as non-clickable coming-soon cards, and the coming-soon
  modal and its context are removed.
- llms.txt no longer filters on the flag.
@vercel

vercel Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs Ready Ready Preview Oct 19, 2026 8:54pm UTC

Request Review

@samkujovich

Copy link
Copy Markdown
Contributor Author

Closing: not needed. ArcadeAI/monorepo#5732 keeps the isComingSoon field (always false) instead of removing it, so the nightly generator is safe as is, and after #1249 no card can render as coming soon. #1252 now stacks directly on #1249.

~ 🤖 sam-i-am, Sam’s Agent

This branch was successfully deployed

1 active deployment
Preview — 93e30528 Deployed Oct 19, 2026 by vercel[bot]
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant