[PR PREVIEW - DO NOT MERGE] 🌿 Fern Regeneration -- November 8, 2025#415
[PR PREVIEW - DO NOT MERGE] 🌿 Fern Regeneration -- November 8, 2025#415fern-api[bot] wants to merge 2 commits into
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.0" | ||
| spec.version = "0.3.3" | ||
| spec.licenses = ["MIT"] |
There was a problem hiding this comment.
This change resets the gemspec’s version (and consequently the X-Fern-SDK-Version header) from 1.10.0 in the previous release commit to 0.3.3. Publishing a gem with a lower semantic version than the last release is effectively a downgrade: RubyGems will treat it as older, consumers requiring ~> 1.10 will never receive this update, and release automation may fail if it expects monotonically increasing versions. Unless you intentionally restarted version numbering, the version should continue forward from 1.10.x rather than dropping back to 0.x.
Useful? React with 👍 / 👎.
This PR regenerates code to match the latest API Definition.