Skip to content

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 13 to 15
spec.name = "vellum_ai"
spec.version = "1.10.0"
spec.version = "0.3.3"
spec.licenses = ["MIT"]

Choose a reason for hiding this comment

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

P1 Badge Avoid downgrading gem version to 0.3.3

The gem specification now sets spec.version to "0.3.3" (and the request headers use the same value), whereas the previous release was 1.10.0. Releasing a new build with a lower version will be rejected by RubyGems and prevents clients pinned to ≥1.10 from upgrading to the regenerated API. Unless the intention is to rewrite history, this should be bumped forward from 1.10.0 rather than reset to a 0.x value.

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