feat(components): backfill AI-optimized ai field (batch 3/5) - #21874
Merged
Conversation
DJ-4272 backfill, batch 3 of 5. Sets the top-level `ai: "optimized"` field on 200 AI-optimized actions across 13 apps, replaces any legacy `// x-pd-ai: optimized` marker comment, and patch-bumps each component and app package.json version. Apps: box,google_contacts google_docs,google_sheets intercom,ironclad jira_service_desk,openphone pipedrive,ramp ramp_sandbox,sharepoint whoisfreaks Batched at <=200 components per the deployment publish cap; the 5 batches touch disjoint apps and can merge independently.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
dannyroosevelt
moved this to Ready for PR Review
in Component (Source and Action) Backlog
Collaborator
|
Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified. |
Collaborator
|
Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:
|
Contributor
|
Important Review skippedToo many files! This PR contains 213 files, which is 63 over the limit of 150. To get a review, reduce the PR to 150 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to Team to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Essentials Run ID: 📒 Files selected for processing (213)
You can disable this status message by setting the Comment |
github-project-automation
Bot
moved this from Ready for PR Review
to Done
in Component (Source and Action) Backlog
|
why you have added ai: "optimized" field, and you know right whenever someones are using your schemas with paid subscription you have to let them know what are the changes. These things cause tool call crashes. |
Collaborator
Can you elaborate on what the issue is re: tool call crashes? That field is not exposed in the tool definition from the MCP server, but I'd love to hear more about what the concern is from your perspective. |
|
Thanks Danny. Let me clarify: we’re seeing production tool-call failures, specifically timeouts—not a schema parser crashing because it received an extra ai property. I should distinguish the observed failure from the suspected cause.
|
Collaborator
Got it, thanks for the additional context. We're taking a look. |
Collaborator
This should be fixed now, can you try again? |
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
4 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.
DJ-4272 backfill, batch 3 of 5 (continues canary #21870).
Sets the top-level
ai: "optimized"field on 200 AI-optimized actions across 13 apps, replaces any legacy// x-pd-ai: optimizedmarker comment with the real field, and patch-bumps each touched component + apppackage.json(required bycheck_version).Batched at ≤200 components per the deployment publish cap. The 5 batches cover disjoint apps, so they can merge independently in any order.
Apps: box,google_contacts google_docs,google_sheets intercom,ironclad jira_service_desk,openphone pipedrive,ramp ramp_sandbox,sharepoint whoisfreaks