Skip to content

Request: Please update CPAN with v0.22 #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ahmogit opened this issue May 22, 2025 · 2 comments
Open

Request: Please update CPAN with v0.22 #10

ahmogit opened this issue May 22, 2025 · 2 comments

Comments

@ahmogit
Copy link

ahmogit commented May 22, 2025

CPAN still has 0.21.

Thanks!

@ahmogit ahmogit changed the title Request: Please pdate CPAN with v0.22 Request: Please update CPAN with v0.22 May 22, 2025
@Ovid
Copy link
Collaborator

Ovid commented May 22, 2025

Hi @ahmogit. I've not yet released because of this bug report I just filed with OpenAI. As a quick fix, I've found that s/3\.0\.0/3.1.0/ in the OpenAI spec fixes the issue, though it's not entirely clear why since the OpenAI spec uses a mixture of features from both versions.

@ahmogit
Copy link
Author

ahmogit commented May 22, 2025

@Ovid Thanks for the quick fix on that; can confirm it works for me as well (though I too am puzzled as to why it works, given the admixture of 3.0.0 and 3.1.0 constructs present in the yaml). Will be interesting to hear OpenAI 's response to your bug report.

Imo, they have been over-lax with their spec versioning, to put it politely. They don't even seem to be bumping their internal version in the "info" section consistently. The changes made in that latest commit were extensive, yet the version ID remained at 2.3.0. I dunno, perhaps there's a good reason for not bumping the version that I simply don't understand, but it sure seems like poor practice to me.

I've been doing battle with this issue -- yaml validation errors on that latest openapi.yaml -- all day. My assumption was that v0.22 worked with that latest openapi.yaml commit, but now I see (just as you said in the bug report) that v0.22 was failing its own chat completion test with openapi version set to 3.0.0, as it currently is.

Anyway, thanks for the quick response and the 3.0.0 -> 3.1.0 workaround, that gets me back on the air for what I was doing. Hopefully OpenAI properly addresses the spec issue soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants