Skip to content

[PR PREVIEW - DO NOT MERGE] 🌿 Fern Regeneration -- November 10, 2025#848

Open
fern-api[bot] wants to merge 2 commits intomainfrom
fern-bot/2025-11-10T23-33Z
Open

[PR PREVIEW - DO NOT MERGE] 🌿 Fern Regeneration -- November 10, 2025#848
fern-api[bot] wants to merge 2 commits intomainfrom
fern-bot/2025-11-10T23-33Z

Conversation

@fern-api
Copy link
Contributor

@fern-api fern-api bot commented Nov 10, 2025

This PR regenerates code to match the latest API Definition.

@vellum-automation vellum-automation bot changed the title 🌿 Fern Regeneration -- November 10, 2025 [PR PREVIEW - DO NOT MERGE] 🌿 Fern Regeneration -- November 10, 2025 Nov 10, 2025
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines 291 to +294
// Either the Vellum-generated ID or the originally specified name that uniquely identifies the Document Index to which you'd like to add the Document.
id string,
// Either the Vellum-generated ID or the originally supplied external_id that uniquely identifies the Document you'd like to add.
documentId string,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid swapping parameter order in AddDocument API

The signature of AddDocument now accepts id before documentId, whereas the previous release accepted the document ID first. Existing callers compiled against v1.10.0 will still compile against v1.10.1 but will send arguments in the old order, causing the generated path to treat a document ID as the index ID (and vice versa), which will hit the wrong resource or return 404s. The same swap occurs in other endpoints (RemoveDocument, WorkflowDeploymentEventExecution, etc.), making this a breaking change in a patch release unless all consumers adjust their call sites.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants