Skip to content

chore: Update platform types #2487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
braintrust-bot wants to merge 1 commit into
base: main
Choose a base branch
from
+350 −46
Open

chore: Update platform types #2487

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
128 changes: 122 additions & 6 deletions generated_types.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3928,6 +3928,34 @@
}
]
},
"NamedScore": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"score": {
"anyOf": [
{
"type": "number",
"minimum": 0,
"maximum": 1
},
{
"type": "boolean"
},
{
"type": "null"
}
]
},
"metadata": {
"type": "object",
"additionalProperties": {}
}
},
"required": ["name"]
},
"NullableSavedFunctionId": {
"anyOf": [
{
Expand Down Expand Up @@ -4133,6 +4161,14 @@
"format": "date-time",
"description": "Date of organization creation"
},
"archived_at": {
"type": ["string", "null"],
"format": "date-time"
},
"deleted_at": {
"type": ["string", "null"],
"format": "date-time"
},
"image_rendering_mode": {
"$ref": "#/components/schemas/ImageRenderingMode"
}
Expand Down Expand Up @@ -4412,7 +4448,7 @@
"type": "string",
"minLength": 1,
"maxLength": 10000,
"description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report."
"description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report."
}
},
"required": ["type", "workspace_id", "channel"]
Expand Down Expand Up @@ -4699,7 +4735,7 @@
"type": "string",
"minLength": 1,
"maxLength": 10000,
"description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report."
"description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report."
}
},
"required": ["type", "workspace_id", "channel"]
Expand All @@ -4721,6 +4757,18 @@
}
],
"description": "The configuration for the automation rule"
},
"runtime_block": {
"type": "object",
"properties": {
"reason": {
"type": "string"
},
"model": {
"type": "string"
}
},
"required": ["reason", "model"]
}
},
"required": ["id", "project_id", "name", "config"]
Expand Down Expand Up @@ -5296,6 +5344,10 @@
"type": ["boolean", "null"],
"description": "If true, use metrics.start rather than created for monitor chart time bucket dimensions."
},
"coding_agent_insights_dashboard": {
"type": ["boolean", "null"],
"description": "If true, enable the agent insights dashboard for this project."
},
"blind_reviews": {
"type": ["boolean", "null"],
"description": "If true, hide peer review scores, comments, and aggregate results from reviewers without project update permissions until they submit their own review."
Expand Down Expand Up @@ -6307,6 +6359,68 @@
}
]
},
"ScoreObject": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "The score name. Defaults to the function name for a single score."
},
"score": {
"anyOf": [
{
"type": "number",
"minimum": 0,
"maximum": 1
},
{
"type": "boolean"
},
{
"type": "null"
}
]
},
"metadata": {
"type": "object",
"additionalProperties": {}
}
},
"required": ["score"]
},
"ScoreResult": {
"anyOf": [
{
"$ref": "#/components/schemas/ScoreObject"
},
{
"$ref": "#/components/schemas/NamedScore"
},
{
"anyOf": [
{
"type": "number",
"minimum": 0,
"maximum": 1
},
{
"type": "boolean"
}
]
},
{
"type": "array",
"items": {
"$ref": "#/components/schemas/NamedScore"
},
"description": "Multiple scores. Each score must have a unique name."
},
{
"type": "null"
}
],
"description": "The return value of a scorer function."
},
"ServiceToken": {
"type": "object",
"properties": {
Expand Down Expand Up @@ -6443,7 +6557,9 @@
"facet",
"preprocessor",
"classifier",
"review"
"review",
"question",
"log"
],
"description": "Type of the span, for display purposes only"
},
Expand Down Expand Up @@ -6616,7 +6732,7 @@
"relabel_overlap_seconds": {
"type": ["number", "null"],
"minimum": 60,
"description": "How much recent history to relabel after a new topic map version becomes active"
"description": "Deprecated. How much recent history to relabel after a new topic map version becomes active. Data planes v2.15.0 and later ignore this and apply a topic map version after the first only to traces classified once it is active."
},
"backfill_time_range": {
"anyOf": [
Expand Down Expand Up @@ -6743,7 +6859,7 @@
"type": "string",
"minLength": 1,
"maxLength": 10000,
"description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report."
"description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report."
}
},
"required": ["type", "workspace_id", "channel"],
Expand Down Expand Up @@ -7615,7 +7731,7 @@
"type": "string",
"minLength": 1,
"maxLength": 10000,
"description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report."
"description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report."
}
},
"required": ["type", "workspace_id", "channel"]
Expand Down
Loading
Loading