Merge dev-v3.2.0 into dev - #320
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rollup of the v3.2.0 work that has landed on
dev-v3.2.0since #301 merged.What it brings
teradatatype, requiredhost, optionalport(default1025) anddatabase.ingres,vectorwise,versantandpoet, plusfastobjectsas a synonym ofpoetandbtrieveas a synonym ofzen.Both schema files stay in lockstep; every new server type ships with docs, a positive example, and a negative test.
Merge
Clean merge this time — no conflicts to resolve.
devcontributed only the sync-main-into-dev merge (#316), which does not touch the same regions.Validation
validate-negative.shandvalidate-examples.shboth run clean on the merged tree against both schema files (JSON_SCHEMA_VERSIONunset and=latest) — four runs,Total failed=0, exit 0 each.🤖 Generated with Claude Code
https://claude.ai/code/session_01An6KmURPXG4Y8uDwd15Roq