chore: prepare CHANGELOG for v3.10.0 release - #195
Merged
Conversation
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
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.
Splits
## [Unreleased]into## [3.10.0] - 2026-09-09. No code changes.What's in v3.10.0
feat:WithPlaceholderStyle— render?for callers whose driver rebinds placeholders (GORM,sqlx.Rebind, squirrel)fix:has()detects JSON columns from the schema, not a hardcoded name listfix: comprehension JSON access derives from the range, not variable namesTogether, #193 and #194 remove the last hardcoded column- and variable-name lists from the converter, completing the sweep started in #62 (#61, #59):
$ grep -rn '\[\]string{"' --include='*.go' . | grep -v _test | grep -v /examples/ $Minor, not major
Two BREAKING behaviour notes are recorded under
### Changed, but both stay within/v3per the skill's rule — the same call made for #113, whose heuristic removal was BREAKING with a niche blast radius. Neither changes an exported signature:has()on a JSON column now requires the column to be declared viaWithSchemasorWithJSONVariables.Callers already passing schemas are unaffected; those with JSON columns outside the old seven names get correct SQL for the first time.
🤖 Generated with Claude Code