-
Notifications
You must be signed in to change notification settings - Fork 217
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
openapi spec generated by Kiota is in version 3.0.4 #5944
Comments
Hi @KennethBWSong The version being emitted is hardcoded in the library used to parse/serialize documents I'd also argue that upgrading the version is the correct behaviour since the document has been parsed, modified in memory, and serialized according to the latest version of the specification. Can you please expand on why this patch version is a problem? For reference, the previously emitted version was 3.0.1 (so not the original version of the document either). |
For other readers, this is an issue because the OP's parsing library hasn't updated their version check. PR has been sent. |
Dependency was released |
What are you generating using Kiota, clients or plugins?
Kiota plugin
In what context or format are you using Kiota?
Source Build
Client library/SDK language
None
Describe the bug
When trying TTK with latest prelease kiota extension (1.22.24122701), we found the version in openapi spec generated under tmp/kiota-xxx/appPackage is "3.0.4", however the version in original openapi spec is "3.0.0".
Kiota generated:
originial:
Expected behavior
Kiota should generate the openapi with same version of original file
How to reproduce
Create a DC + Plugin from TTK
Select OpenAPI Spec
Choose a local openapi spec with version 3.0.0
Click generate and create TTK project.
Open API description file
No response
Kiota Version
v1.22.0-preview.202412260001
Latest Kiota version known to work for scenario above?(Not required)
No response
Known Workarounds
No response
Configuration
No response
Debug output
Click to expand log
```The text was updated successfully, but these errors were encountered: