Fixing issues with github actions when generating docs and toolkit changes detectiong#780
Open
Fixing issues with github actions when generating docs and toolkit changes detectiong#780
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
jottakka
changed the title
jottakka
changed the title
Remove databases _meta.tsx and restore integrations and development _meta.tsx files to match main. Co-authored-by: Cursor <cursoragent@cursor.com>
Restore all toolkit JSON data files to match main. Co-authored-by: Cursor <cursoragent@cursor.com>
toolkit-docs-generator/tests/workflows/generate-toolkit-docs.test.ts
Outdated
Show resolved
Hide resolved
Co-authored-by: jottakka <203343514+jottakka@users.noreply.github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| "!node_modules", | ||
| "!public", | ||
| "!toolkit-docs-generator/data/toolkits", | ||
| "!toolkit-docs-generator/data/toolkits", |
There was a problem hiding this comment.
Duplicate ignore pattern in biome config
Low Severity
The "!toolkit-docs-generator/data/toolkits" ignore pattern appears twice in the files.includes array. One of the duplicate entries can be removed.
sdserranog
reviewed
Feb 19, 2026
| import { withLlmsTxt } from "./lib/next-plugin-llmstxt"; | ||
| import { remarkGlossary } from "./lib/remark-glossary"; | ||
|
|
||
| const require = createRequire(import.meta.url); |
Contributor
There was a problem hiding this comment.
Not sure why we are adding all of these.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Note
Medium Risk
Touches CI automation and the toolkit docs generator’s diff/verification logic; mistakes could lead to missed regenerations or unexpected docs/route changes, but scope is limited to docs tooling (not runtime auth/data paths).
Overview
Toolkit docs automation is hardened and made more deterministic. The
generate-toolkit-docsGitHub Action now runs nightly on a schedule, invokes the generator viapnpm dlx tsxagainst the Enginetool-metadataAPI with--require-complete/--verbose, avoids pruning empty integration sections by default, and disables Husky when auto-opening PRs (also updating the auto PR title/commit message).Change detection and output verification are made resilient to schema drift. The generator/verification pipeline can now parse “legacy” toolkit JSON via a new fallback parser (
parsePreviousToolkitForDiff) and optionally allow that fallback during diffing/verification, while tool change signatures are normalized to ignore source-unstable fields (descriptions, oauth provider IDs, empty enums vs null, andunknownoutput types).Design system loading and route/category resolution are stabilized. Design-system imports are switched to a
require.resolve-based loader with Next webpack aliases,listToolkitRoutesnow treats generated toolkit JSON as the source of truth forcategory/docsLink/isHidden(catalog as fallback), andsync-toolkit-sidebaradds--remove-empty-sections[=true|false](with--pruneas an alias) so category removal is opt-in.Misc reliability tweaks. Pre-commit uses
pnpm execand avoids stash/pop conflicts with partially staged files, external URL tests add retries for transient failures, and the design system dependency is bumped.Written by Cursor Bugbot for commit 44108b6. This will update automatically on new commits. Configure here.