This repository was archived by the owner on Oct 27, 2026. It is now read-only.
Repository navigation
refactor(integrations): stop relying on the coming-soon flag - #1251
Closed
samkujovich wants to merge 1 commit into
Closed
samkujovich wants to merge 1 commit into
samkujovich wants to merge 1 commit into
Conversation
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.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of GRO-615
What/why
Arcade no longer lists "coming soon" toolkits: ArcadeAI/monorepo#5732 deletes the 37 placeholders from design-system, and
isComingSoonisfalseon 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
isComingSoonis removed from its schemas, merger, and freshness check. Zod drops unknown keys, so it accepts branding with or without the field.isComingSoon: falseon the two partner toolkits, because the design-systemToolkittype requires it. Docs' ownToolkitWithDocsLinkomits it, so nothing in docs reads it.Proof
isComingSoonpublic-catalog-api.test.tsfeeds branding that still carries the field; the existing fixtures, now without it, also passresolveIndexToolkitstests inintegration-index-links.test.ts; the live-data tests confirm every card links to an existing pagepnpm test(900 passed),pnpm lint,tsc --noEmitAdditional notes
Notify me clickedevent with the visitor's email. That event stops, andTool card clickedloses itsis_coming_soonproperty, which was alwaysfalseafter fix(integrations): list the toolkits the public catalog publishes #1249.isComingSoonline, so the first generated PR after this merges touches every toolkit file by one line.~ 🤖 sam-i-am, Sam’s Agent