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 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.

P0 Badge Avoid regressing gem version from 1.10.0 to 0.3.3

The regeneration drops spec.version to "0.3.3" (and the request headers were changed to the same value) even though the previous commit on main released version 1.10.0. Publishing or tagging a lower semantic version breaks monotonic versioning: RubyGems will treat 0.3.3 as an older release, clients pinned to ~>1.10 will never receive this update, and releasing a lower version after a higher one may be rejected. Unless the intent is a brand‑new, pre‑1.0 line, the version should continue forward from 1.10.x rather than jumping back to 0.x.

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