Quick one. lib/openai/assistants.rb, threads.rb, messages.rb, runs.rb and run_steps.rb all wrap
the Assistants API, and OpenAI shuts the whole thing down on Aug 26. assistants.rb:6 is
client.beta(assistants: OpenAI::Assistants::BETA_VERSION) and runs.rb:29 posts to /threads/runs.
The part that made me write this: it breaks for everyone downstream rather than for you. 136 gems
depend on ruby-openai and the README still teaches client.assistants.create, so anyone following
the docs after the 26th gets a 404 with nothing pointing at why.
No idea what the right call is for a library, whether that's a deprecation warning, a Responses-backed shim, or just a README note, and that's your judgement not mine. Happy to send a PR for whichever you'd want. I'm building a scanner for retired model ids and endpoints and this is the highest-blast-radius thing it has found so far.
Quick one. lib/openai/assistants.rb, threads.rb, messages.rb, runs.rb and run_steps.rb all wrap
the Assistants API, and OpenAI shuts the whole thing down on Aug 26. assistants.rb:6 is
client.beta(assistants: OpenAI::Assistants::BETA_VERSION) and runs.rb:29 posts to /threads/runs.
The part that made me write this: it breaks for everyone downstream rather than for you. 136 gems
depend on ruby-openai and the README still teaches client.assistants.create, so anyone following
the docs after the 26th gets a 404 with nothing pointing at why.
No idea what the right call is for a library, whether that's a deprecation warning, a Responses-backed shim, or just a README note, and that's your judgement not mine. Happy to send a PR for whichever you'd want. I'm building a scanner for retired model ids and endpoints and this is the highest-blast-radius thing it has found so far.