[codex] Remove unsupported 1.8.x string specs#43
Merged
ChiragAgg5k merged 1 commit intomainfrom Mar 29, 2026
Merged
Conversation
|
Important Review skippedToo many files! This PR contains 228 files, which is 78 over the limit of 150. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (228)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Remove unsupported
longtext,mediumtext,text, andvarcharstring variants from the1.8.xspecs for both legacydatabasesattributes andtablesdbcolumns.What Changed
databasesattribute endpoints forlongtext,mediumtext,text, andvarchartablesdbcolumn endpoints for the same four string variants1.8.xspec artifactsexamples/1.8.xWhy
These string attribute/column variants should not exist in the
1.8.xline. This change reverts them from the published spec surface and generated examples.Impact
1.8.xconsole/server OpenAPI and Swagger specs no longer advertise these unsupported endpoints1.8.xexamples no longer include SDK snippets for these unsupported operations1.8.xclient spec files were left unchanged because they did not contain these entriesValidation
databasesCreate/Update{Longtext|Mediumtext|Text|Varchar}AttributeortablesDBCreate/Update{Longtext|Mediumtext|Text|Varchar}Columnremain inspecs/1.8.xHEADand verified only the intended 16 path removals and 8 schema/definition removals occurred per file, with no otherpathsor schema/definition changesexamples/1.8.xNotes
The raw textual diff in the JSON spec files is larger than the logical change because the files were reserialized while preserving the same semantic content outside the targeted removals.