Skip to content

Conversation

@fern-api
Copy link
Contributor

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

This PR regenerates code to match the latest API Definition.

@vellum-automation vellum-automation bot changed the title 🌿 Fern Regeneration -- November 8, 2025 [PR PREVIEW - DO NOT MERGE] 🌿 Fern Regeneration -- November 8, 2025 Nov 8, 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 12 to +14
Gem::Specification.new do | spec |
spec.name = "vellum_ai"
spec.version = "1.10.0"
spec.version = "0.3.3"

Choose a reason for hiding this comment

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

P1 Badge Keep SDK version monotonically increasing

The commit changes spec.version to "0.3.3" and updates the request headers to advertise the same value even though the previous release in this repository was 1.10.0. Publishing a gem with a lower version number will be treated as a downgrade by Bundler/RubyGems, so clients already on 1.10.x will never pick up this regeneration and automated release tooling that expects version bumps may fail. If this regeneration is meant to be the next release after 1.10.0, the version should advance (e.g. 1.10.1) rather than reset to 0.3.3.

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.

1 participant