[PR PREVIEW - DO NOT MERGE] 🌿 Fern Regeneration -- November 11, 2025 #429
Conversation
vellum-automation
bot
changed the title
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 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".
| Gem::Specification.new do | spec | | ||
| spec.name = "vellum_ai" | ||
| spec.version = "1.10.1" | ||
| spec.version = "0.3.3" | ||
| spec.licenses = ["MIT"] | ||
| spec.authors = Vellum::Gemconfig::AUTHORS |
There was a problem hiding this comment.
The regeneration drops the gem specification and SDK header version to 0.3.3 even though the repository has been publishing from the 1.10.x line. Shipping this change would make the next release appear older than existing builds, so dependency resolvers will not upgrade and the embedded version header will misreport the client’s version. Unless the intent is to revert to a pre‑1.0 series, keep the version at 1.10.x or bump it forward instead of backwards.
Useful? React with 👍 / 👎.
| # api_key: "YOUR_API_KEY" | ||
| # ) | ||
| # api.execute_api(url: "x") | ||
| def execute_api(url:, method: nil, body: nil, headers: nil, bearer_token: nil, request_options: nil) | ||
| def execute_api(url:, method_: nil, body: nil, headers: nil, bearer_token: nil, request_options: nil) |
There was a problem hiding this comment.
Vellum::Client#execute_api now takes a keyword method_ instead of the previously released method. Existing callers invoking execute_api(url: ..., method: "GET") will start raising ArgumentError: unknown keyword :method after upgrading. Unless you are planning a breaking major release, keep the method: keyword (or alias it) and map it internally to avoid breaking current integrations; the async version of this method has the same issue.
Useful? React with 👍 / 👎.
This PR regenerates code to match the latest API Definition.