Repository navigation
chore(release): v0.5.1 - #131
Merged
Merged
Conversation
The aggregate Expression helpers render SurrealQL's own aggregates (count(), math::sum / mean / min / max) instead of SQL spellings the server rejects at parse time. The surrealdb.go requirement moves to v1.7.0. Patch rather than minor: no signature changes. Every rendering that changes was either refused by the server outright or, for Count(f), an equivalent spelling of the same aggregate.
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.
Cuts 0.5.1. Six commits since v0.5.0.
Fixed
Expressionhelpers rendered SQL that SurrealDB rejects at parse time:Count("")emittedCOUNT(*)andSum/Avg/MinFn/MaxFnemittedSUM/AVG/MIN/MAX. They now rendercount()andmath::sum/math::mean/math::min/math::max(fix(query): render SurrealQL aggregates instead of SQL ones #130)Changed
github.com/surrealdb/surrealdb.gov1.6.0 -> v1.7.0 (chore(deps): bump github.com/surrealdb/surrealdb.go from 1.6.0 to 1.7.0 in the gomod-minor-patch group #128), so consumers now resolve at least v1.7.0Not user-facing
ExecuteMigrationrestructured so gofmt 1.26 and 1.27 agree on its formatting; behaviour unchanged (style(migration): keep executor returns stable across gofmt 1.26 and 1.27 #129)actions/checkout,actions/setup-goandactions/setup-pythonbumped to v7 (chore(deps): bump actions/checkout from 6 to 7 #125, chore(deps): bump actions/setup-go from 6 to 7 #126, chore(deps): bump actions/setup-python from 6 to 7 #127)Why patch
No signature changes. Every rendering that changes was either refused by the server outright or, for
Count(f), an equivalent spelling of the same aggregate.surql.Versionmoves to0.5.1; the[Unreleased]changelog section becomes[0.5.1] - 2026-10-03and gains the driver bump under Changed.Verified locally on this branch
gofmt -l .clean under Go 1.26.1 and 1.27.1;go vet ./...,go build ./...cleango test ./...passes under Go 1.26.1 and 1.27.1 (no-racelocally: no cgo on the Windows host)go test -tags=integration ./...againstsurrealdb/surrealdb:v3.0.5(the CI image, same start command): all packages pass