🌿 Fern Regeneration -- November 8, 2025 #416
Conversation
![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".
| unless request_options&.api_version.nil? | ||
| req.headers["X-API-Version"] = request_options.api_version | ||
| else | ||
| req.headers["X-API-Version"] = "2025-07-30" | ||
| end |
There was a problem hiding this comment.
Calls now set req.headers["X-API-Version"] only when the caller passes an explicit api_version. The previous implementation always fell back to "2025-07-30" so that the generated client targeted the API version it was built against. With the fallback removed, Vellum::Client.new(api_key: ...) sends no version header at all, leaving requests at whatever default the server chooses. If the server default is older or changes in the future, responses will no longer match the 2025‑07‑30 shapes baked into this SDK and requests that rely on newer endpoints can start failing unless every consumer manually supplies an api_version. Restoring the default header or defaulting the client constructor keeps behavior stable.
Useful? React with 👍 / 👎.
| Gem::Specification.new do | spec | | ||
| spec.name = "vellum_ai" | ||
| spec.version = "1.10.0" | ||
| spec.version = "0.3.3" | ||
| spec.licenses = ["MIT"] |
There was a problem hiding this comment.
The gemspec now advertises version "0.3.3" even though the current release series is 1.x. RubyGems requires monotonically increasing versions, so dropping the version means this package cannot be published or consumed as an upgrade, and clients would appear to downgrade unexpectedly. The version should move forward (e.g. 1.10.1) instead of reverting to a much older number.
Useful? React with 👍 / 👎.
This PR regenerates code to match the latest API Definition.