chore(deps): bump the go-modules group across 1 directory with 24 updates

[dependabot]

Bumps the go-modules group with 20 updates in the / directory:

Package	From	To
github.com/knadh/koanf/parsers/yaml	1.1.0	1.1.1
github.com/knadh/koanf/providers/posflag	1.0.1	1.0.2
github.com/knadh/koanf/providers/structs	1.0.0	1.0.1
github.com/knadh/koanf/v2	2.3.5	2.3.6
github.com/nats-io/nats-server/v2	2.14.3	2.14.4
github.com/redis/go-redis/v9	9.21.0	9.22.0
google.golang.org/grpc	1.82.1	1.83.0
gorm.io/driver/postgres	1.6.0	1.6.2
gorm.io/driver/sqlserver	1.6.3	1.6.4
modernc.org/sqlite	1.54.0	1.56.0
github.com/aws/aws-sdk-go-v2	1.43.0	1.43.4
github.com/aws/aws-sdk-go-v2/config	1.32.31	1.32.35
github.com/aws/aws-sdk-go-v2/feature/rds/auth	1.6.31	1.6.35
github.com/eko/gocache/lib/v4	4.2.3	4.2.4
github.com/lestrrat-go/jwx/v3	3.1.1	3.2.0
go.opentelemetry.io/contrib/bridges/otellogrus	0.19.0	0.20.0
go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho	0.69.0	0.70.0
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp	0.69.0	0.70.0
go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp	0.20.0	0.21.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp	1.44.0	1.45.0

Updates github.com/knadh/koanf/parsers/yaml from 1.1.0 to 1.1.1

Release notes

Sourced from github.com/knadh/koanf/parsers/yaml's releases.

v1.1.1

• 57e89cf Merge pull request #94 from knadh/fix-posflag-callbacks
• d3bad45 Merge pull request #91 from knadh/bug-report-template
• b1985ad Merge pull request #93 from rhnvrm/unit-test-issue-90
• a72baa3 Merge pull request #92 from knadh/fix-posflag-callbacks
• adc0b54 tests: add unit test for #90
• 9e87eba Fix unchanged default posflag value merging via incorrect callback.
• 2f82a14 Merge pull request #87 from mvrahden/feature/filesystem
• 6e9c0a7 Add github issue templates
• 023ecc6 Update README with fs.FS provider
• f7e28d0 fix call to Close on file descriptor
• caeef66 Merge pull request #1 from rhnvrm/feature/filesystem
• 02f42ea fix: add build constraints to maintain compat
• 149144c add fs.FS provider
• 139fe40 Merge pull request #85 from mvrahden/fix/base_test
• 7cc3416 move error assertions and make them error-type dependent
• 0a31536 fix race condition and reduce test time by half
• af2e3f4 simplify and unify test arrangements
• aa62c04 update testify to v1.7.0
• 5234867 Merge pull request #84 from mr-karan/gh_actions
• c79fbc5 feat: Replace Travis with GitHub Actions

Commits

• 57e89cf Merge pull request #94 from knadh/fix-posflag-callbacks
• d3bad45 Merge pull request #91 from knadh/bug-report-template
• b1985ad Merge pull request #93 from rhnvrm/unit-test-issue-90
• a72baa3 Merge pull request #92 from knadh/fix-posflag-callbacks
• adc0b54 tests: add unit test for #90
• 9e87eba Fix unchanged default posflag value merging via incorrect callback.
• 2f82a14 Merge pull request #87 from mvrahden/feature/filesystem
• 6e9c0a7 Add github issue templates
• 023ecc6 Update README with fs.FS provider
• f7e28d0 fix call to Close on file descriptor
• Additional commits viewable in compare view

Updates github.com/knadh/koanf/providers/posflag from 1.0.1 to 1.0.2

Commits

• See full diff in compare view

Updates github.com/knadh/koanf/providers/structs from 1.0.0 to 1.0.1

Commits

• 75e13d9 Fix multiple large int64 handling issues.
• b133504 skip disabled secret on azure kv read (#437)
• 1aba4ed deps: upgrade go-toml to v2.4.3 (#419)
• d2ffdaa Bump golang.org/x/crypto from 0.45.0 to 0.52.0 in /providers/kiln (#427)
• 4f7edbb Bump google.golang.org/grpc from 1.56.3 to 1.82.1 in /examples (#430)
• 31dd449 fix: error on scalar/map type mismatch in MergeStrict regardless of order (#424)
• e09e4c8 fix: report full key var in MergeStrict type-mismatch error message (#418)
• 7a28d59 Exclude nats, vault providers from global workspace and fix CI test commands.
• d511690 Fix test action to use local Go toolchain for different versions.
• 308274c Fix async file provider Watch() test that would race and fail randomly.
• Additional commits viewable in compare view

Updates github.com/knadh/koanf/v2 from 2.3.5 to 2.3.6

Release notes

Sourced from github.com/knadh/koanf/v2's releases.

v2.3.6

What's Changed

• fix: error on scalar/map type mismatch in MergeStrict regardless of order by @​upuddu in knadh/koanf#424
• Bump google.golang.org/grpc from 1.56.3 to 1.82.1 in /examples by @​dependabot[bot] in knadh/koanf#430
• Bump golang.org/x/crypto from 0.45.0 to 0.52.0 in /providers/kiln by @​dependabot[bot] in knadh/koanf#427
• deps: upgrade go-toml to v2.4.3 by @​GreyXor in knadh/koanf#419
• skip disabled secret on azure kv read by @​genlp in knadh/koanf#437

New Contributors

• @​upuddu made their first contribution in knadh/koanf#424
• @​genlp made their first contribution in knadh/koanf#437

Full Changelog: knadh/koanf@v2.3.5...v2.3.6

Commits

• 75e13d9 Fix multiple large int64 handling issues.
• b133504 skip disabled secret on azure kv read (#437)
• 1aba4ed deps: upgrade go-toml to v2.4.3 (#419)
• d2ffdaa Bump golang.org/x/crypto from 0.45.0 to 0.52.0 in /providers/kiln (#427)
• 4f7edbb Bump google.golang.org/grpc from 1.56.3 to 1.82.1 in /examples (#430)
• 31dd449 fix: error on scalar/map type mismatch in MergeStrict regardless of order (#424)
• See full diff in compare view

Updates github.com/nats-io/nats-server/v2 from 2.14.3 to 2.14.4

Release notes

Sourced from github.com/nats-io/nats-server/v2's releases.

Release v2.14.4

Changelog

Refer to the 2.14 Upgrade Guide for backwards compatibility notes with 2.12.x. Please note that the 2.13.x version was skipped.

Go Version

• 1.26.5 (#8435)

Dependencies

• github.com/klauspost/compress v1.19.0 (#8385)
• golang.org/x/crypto v0.54.0 (#8385)
• golang.org/x/sys v0.47.0 (#8385)
• github.com/antithesishq/antithesis-sdk-go v0.7.2-default-no-op (#8385)

Improved

JetStream

• The Raft transport layer has been decoupled, improves testing but does not change server behaviour (#8181)
• The disk concurrency semaphore has been increased to 4096 slots, up from the previous CPU-scaled count (#8336)
• The disk concurrency semaphore can now be configured with the max_concurrent_io option in the jetstream config block (#8336)
• Filestore underlying block cache buffers are now recycled to the pool when the weak reference is collected by the GC, which should smooth out memory usage with some usage patterns (#8395)
• Calculating and looking up sequences in delete maps for file-backed streams with large numbers of interior deletes is now faster and holds locks for less time (#8403)
• Inserts, iterations and deletes in AVL sequence sets are now faster in many cases, which speeds up the tracking of interior deletes (#8406)
• Stream snapshots now attempt to determine the correct encode buffer size up front, avoiding many unnecessary allocations on streams with large numbers of interior deletes (#8405)
• Reduced memory usage of the structure that is used to track subjects within a stream (#8412)

Fixed

General

• allow_non_tls will no longer log an incorrect message at startup claiming that TLS is required (#8420)
• Combining no_auth_user with auth callouts will no longer skip authentication checks when no CONNECT message is sent
• JWT validation no longer crashes the server with whitespace-only permissions
• Several paths that enforce the permissions of queue subscriptions no longer treat the whole permission as a subject literal
• Several JetStream and MQTT endpoints now correctly guard against null values in JSON
• Fixed an authentication bypass with TLS verify_and_map authenticating users with blank passwords

Monitoring

• The healthz endpoint will now skip and no longer report on expired JWT accounts (#8379, thanks to @​ByapakSigdel)
• The varz endpoint will now correctly report JetStream limits after they were changed via a config reload (#8394)

JetStream

• Malformed cluster replicated acks or delivered updates are now correctly rejected by the decoder (#8284, thanks to @​uwezkhan)
• Malformed cluster replicated skip or reset updates are now correctly rejected by the decoder (#8345, thanks to @​uwezkhan)
• Empty cluster replicated entries are now correctly ignored (#8347, thanks to @​uwezkhan)

... (truncated)

Commits

• bbd6dc5 Release v2.14.4
• 7d26d07 Update to Go 1.26.5/1.25.12
• c7163b2 Release v2.14.4-RC.4
• ee56a6c Cherry-picks for 2.14.4-RC.4 (#147)
• 725f008 [FIXED] Certificate users authenticatable by username on other listeners
• 566e772 [FIXED] Block MQTT subscriptions to internal MQTT subjects
• 43607c4 [FIXED] Consumer assignment proposed without a raft group
• 3b90b2c [FIXED] Panic setting up a stream source/mirror on malformed create response
• f44c537 [FIXED] Panic decoding MQTT retained messages, sessions and JS API replies
• c6c7061 [FIXED] Panic decoding counter source with null entry
• Additional commits viewable in compare view

Updates github.com/redis/go-redis/v9 from 9.21.0 to 9.22.0

Release notes

Sourced from github.com/redis/go-redis/v9's releases.

9.22.0

This is a minor release introducing two flagship (experimental) features — client-side caching and automatic pipelining — alongside support for Redis 8.10, new commands, and a large batch of stability and parser-robustness fixes. It consolidates everything shipped in 9.22.0-beta.1, so the notes below cover the full 9.21.0 → 9.22.0 upgrade.

⚠️ Two changes to be aware of when upgrading from 9.21.0:

• Default configuration values changed (#3918): read/write timeouts, retry backoff, cluster state reload interval, and TCP keep-alive defaults are now aligned with the cross-SDK configuration proposal (see the highlight below). Explicitly configured values are unaffected.
• WaitAOF return type corrected (#3888): WaitAOF now returns *IntSliceCmd, matching the two-integer reply of WAITAOF (previously *IntCmd, which failed to parse the reply at runtime). Code referencing the old return type needs a one-line update.

🚀 Highlights

Client-Side Caching (Experimental)

The standalone Client gains server-assisted client-side caching built on RESP3 CLIENT TRACKING. Enable it by setting ClientSideCacheConfig in Options (or supply your own cache via ClientSideCache — e.g. to share one cache across clients). Cacheable read results are served from a local in-process cache and invalidated automatically when the server reports a change, cutting round trips for read-heavy workloads.

The invalidation architecture is selected by ClientSideCacheStrategy; the default (and currently only) strategy is CSCStrategySharedTracking: one shared cache, every pool connection runs plain CLIENT TRACKING ON, and a background drainer applies buffered invalidations — portable (no BCAST) and consistent with the other Redis client libraries. Requirements and guardrails: RESP3 (Protocol: 3), standalone client, DB 0 only; commands that would change the connection identity (SELECT, AUTH, ...) are rejected while caching is enabled, and CSC is disabled when a credentials provider is set (fixed Username/Password work and are namespaced). See the README's client-side caching section and the runnable example.

Experimental: the API may change in a minor release.

(#3941) by @​ofekshenawa

Automatic Pipelining (Experimental)

AutoPipeliner is a background batcher that coalesces commands from many concurrent goroutines into Redis pipelines, multiplying throughput without any manual pipeline management. It comes in two faces, available on Client and ClusterClient (and configurable via Options.AutoPipelineOptions / UniversalOptions.AutoPipelineOptions):

• AutoPipeline() — the blocking face: a drop-in Cmdable where each call blocks until executed, exactly like a plain client, while concurrent callers' commands batch together under the hood (measured locally over loopback: ~1M+ SET/sec vs ~100k unpipelined; indicative, not a guarantee). Per-goroutine command order is preserved.
• AsyncAutoPipeline() — the deferred face: command calls return immediately and every typed result accessor (Val/Result/Err/...) blocks until the command has executed. Submit a window of commands, then read the results, to keep pipelines deep (~2–3M SET/sec locally; indicative).

AutoPipelineOptions controls batching: MaxBatchSize (soft target, default 200; the blocking face's preset uses 300), MaxBatchBytes (approximate payload cap so huge values flush as several bounded writes), MaxFlushDelay with optional AdaptiveDelay (delay scales down as the queue fills), and MaxConcurrentBatches (default 1 = a single ordered batch stream; raising it requires Unordered: true, so ordering is never lost by accident — Validate() rejects the combination otherwise). A usage tour and throughput comparison live in https://github.com/redis/go-redis/blob/HEAD/example/autopipeline.

Experimental: the API may change in a future release — pin your go-redis version if you adopt it.

(#3942) by @​ndyakov, with help from @​cxljs

Redis 8.10 Support

This release adds support for Redis 8.10. The README's supported-versions list now includes Redis 8.10, and CI runs the full suite against the redislabs/client-libs-test:8.10.0 image by default (#3920, #3940).

Coverage for the new commands and options that ship with Redis 8.10:

• HIMPORT (#3919) — bulk hash import via server-side fieldsets, exposed as HImportPrepare, HImportSet, HImportDiscard, and HImportDiscardAll. Fieldsets are session state scoped to a single physical connection, which does not mix well with connection pooling — so the client keeps a versioned fieldset registry and lazily replays the PREPARE on whichever pooled connection executes a SET that needs it, at most once per connection, with no extra round trip (the PREPARE is injected into the same write as the SET).
• LMOVEM / BLMOVEM (#3913) — move multiple elements between lists in one call.
• SUNIONCARD / SDIFFCARD (#3897) — cardinality of set union/difference without materializing the result.
• XREAD / XREADGROUP MAXCOUNT and MAXSIZE (#3898) — bound how much data a stream read returns.
• TS.READ (#3896), TS.QUERYLABELS (#3926), TS.NRANGE / TS.NREVRANGE (#3870) with multiple aggregators per key (#3937), and EXCLUDEEMPTY on TS.MRANGE / TS.MREVRANGE (#3912) — new time-series query surface.
• FT.ALIASLIST (#3925), COLLECT reducer for FT.AGGREGATE (#3886), RERANK on HNSW vector fields in FT.CREATE (#3927), and FT.HYBRID timeout warnings (#3911) — search coverage.

Cross-SDK Aligned Defaults

Default configuration values now follow the cross-SDK configuration proposal shared by all Redis client libraries (#3918):

... (truncated)

Changelog

Sourced from github.com/redis/go-redis/v9's changelog.

9.22.0 (2026-08-03)

This is a minor release introducing two flagship (experimental) features — client-side caching and automatic pipelining — alongside support for Redis 8.10, new commands, and a large batch of stability and parser-robustness fixes. It consolidates everything shipped in 9.22.0-beta.1, so the notes below cover the full 9.21.0 → 9.22.0 upgrade.

⚠️ Two changes to be aware of when upgrading from 9.21.0:

• Default configuration values changed (#3918): read/write timeouts, retry backoff, cluster state reload interval, and TCP keep-alive defaults are now aligned with the cross-SDK configuration proposal (see the highlight below). Explicitly configured values are unaffected.
• WaitAOF return type corrected (#3888): WaitAOF now returns *IntSliceCmd, matching the two-integer reply of WAITAOF (previously *IntCmd, which failed to parse the reply at runtime). Code referencing the old return type needs a one-line update.

🚀 Highlights

Client-Side Caching (Experimental)

The standalone Client gains server-assisted client-side caching built on RESP3 CLIENT TRACKING. Enable it by setting ClientSideCacheConfig in Options (or supply your own cache via ClientSideCache — e.g. to share one cache across clients). Cacheable read results are served from a local in-process cache and invalidated automatically when the server reports a change, cutting round trips for read-heavy workloads.

The invalidation architecture is selected by ClientSideCacheStrategy; the default (and currently only) strategy is CSCStrategySharedTracking: one shared cache, every pool connection runs plain CLIENT TRACKING ON, and a background drainer applies buffered invalidations — portable (no BCAST) and consistent with the other Redis client libraries. Requirements and guardrails: RESP3 (Protocol: 3), standalone client, DB 0 only; commands that would change the connection identity (SELECT, AUTH, ...) are rejected while caching is enabled, and CSC is disabled when a credentials provider is set (fixed Username/Password work and are namespaced). See the README's client-side caching section and the runnable example.

Experimental: the API may change in a minor release.

(#3941) by @​ofekshenawa

Automatic Pipelining (Experimental)

AutoPipeliner is a background batcher that coalesces commands from many concurrent goroutines into Redis pipelines, multiplying throughput without any manual pipeline management. It comes in two faces, available on Client and ClusterClient (and configurable via Options.AutoPipelineOptions / UniversalOptions.AutoPipelineOptions):

• AutoPipeline() — the blocking face: a drop-in Cmdable where each call blocks until executed, exactly like a plain client, while concurrent callers' commands batch together under the hood (measured locally over loopback: ~1M+ SET/sec vs ~100k unpipelined; indicative, not a guarantee). Per-goroutine command order is preserved.
• AsyncAutoPipeline() — the deferred face: command calls return immediately and every typed result accessor (Val/Result/Err/...) blocks until the command has executed. Submit a window of commands, then read the results, to keep pipelines deep (~2–3M SET/sec locally; indicative).

AutoPipelineOptions controls batching: MaxBatchSize (soft target, default 200; the blocking face's preset uses 300), MaxBatchBytes (approximate payload cap so huge values flush as several bounded writes), MaxFlushDelay with optional AdaptiveDelay (delay scales down as the queue fills), and MaxConcurrentBatches (default 1 = a single ordered batch stream; raising it requires Unordered: true, so ordering is never lost by accident — Validate() rejects the combination otherwise). A usage tour and throughput comparison live in https://github.com/redis/go-redis/blob/master/example/autopipeline.

Experimental: the API may change in a future release — pin your go-redis version if you adopt it.

(#3942) by @​ndyakov, with help from @​cxljs

Redis 8.10 Support

This release adds support for Redis 8.10. The README's supported-versions list now includes Redis 8.10, and CI runs the full suite against the redislabs/client-libs-test:8.10.0 image by default (#3920, #3940).

Coverage for the new commands and options that ship with Redis 8.10:

• HIMPORT (#3919) — bulk hash import via server-side fieldsets, exposed as HImportPrepare, HImportSet, HImportDiscard, and HImportDiscardAll. Fieldsets are session state scoped to a single physical connection, which does not mix well with connection pooling — so the client keeps a versioned fieldset registry and lazily replays the PREPARE on whichever pooled connection executes a SET that needs it, at most once per connection, with no extra round trip (the PREPARE is injected into the same write as the SET).
• LMOVEM / BLMOVEM (#3913) — move multiple elements between lists in one call.
• SUNIONCARD / SDIFFCARD (#3897) — cardinality of set union/difference without materializing the result.
• XREAD / XREADGROUP MAXCOUNT and MAXSIZE (#3898) — bound how much data a stream read returns.
• TS.READ (#3896), TS.QUERYLABELS (#3926), TS.NRANGE / TS.NREVRANGE (#3870) with multiple aggregators per key (#3937), and EXCLUDEEMPTY on TS.MRANGE / TS.MREVRANGE (#3912) — new time-series query surface.
• FT.ALIASLIST (#3925), COLLECT reducer for FT.AGGREGATE (#3886), RERANK on HNSW vector fields in FT.CREATE (#3927), and FT.HYBRID timeout warnings (#3911) — search coverage.

Cross-SDK Aligned Defaults

Default configuration values now follow the cross-SDK configuration proposal shared by all Redis client libraries (#3918):

... (truncated)

Commits

• c7f59a2 chore(release): prepare 9.22.0 (#3947)
• c994cfc feat(autopipeline): automatic command pipelining (#3942)
• 228b463 chore(deps): bump actions/stale from 10 to 11 (#3944)
• a6be850 feat(csc): add standalone client-side caching (#3941)
• 82b0213 chore(release): prepare 9.22.0-beta.1 (#3940)
• 8eb9583 fix(rediscmd): redact credential args in AppendCmd (#3939)
• 90fd088 chore(ci): point 8.10 testing at custom client-libs-test image (#3938)
• 93f961a feat(timeseries): support multiple aggregators per key in TS.NRANGE (#3937)
• 49e0041 feat(himport): HIMPORT command with lazy per-connection prepare (#3919)
• 3dd9675 fix(proto): peek push notification name without demanding 36 bytes (#3936)
• Additional commits viewable in compare view

Updates google.golang.org/grpc from 1.82.1 to 1.83.0

Release notes

Sourced from google.golang.org/grpc's releases.

Release 1.83.0

Security

• server: Stop reading from connections when flooded by HTTP/2 frames to mitigate resource exhaustion. The default value for this limit is 100 frames, excluding DATA and HEADERS, and may be changed by setting environment variable GRPC_GO_EXPERIMENTAL_CONTROL_BUFFER_THROTTLE_LIMIT.
• xds/rbac: Support Metadata and RequestedServerName permissions matcher fields. If present in a DENY rule, previously these would be ignored and fail-open.
• xds/rbac: Fix panic when parsing unsupported fields in NotRule/NotId permissions.
• xds/rbac: Support the deprecated source_ip principal identifier by treating it as equivalent to direct_remote_ip.
• xds: Fix panic when parsing route header matchers configured with empty exact_match, prefix_match, or suffix_match strings. (#9223)

New Features

• xds/googlec2p: Enable DirectPath over Interconnect support for on-premises clients via the force-xds target URI query parameter. (#9133)
• xds: Enable xDS configuration to control which fields get propagated from ORCA backend metric reports to LRS load reports. (#9145)
• authz: Add OnPolicyUpdate callback to FileWatcherOptions to notify when an authz policy is loaded or updated. (#9142)
  • Special Thanks: @​hnefatl
• xds: Add support for the GCP Authentication HTTP Filter, which automatically fetches and attaches GCP Service Account Identity JWT tokens to outgoing RPCs.
  • This feature can be enabled by setting environment variable GRPC_EXPERIMENTAL_XDS_GCP_AUTHENTICATION_FILTER=true. (#9119)
• xds: Add support for xDS-based HTTP CONNECT proxies.
  • This feature can be enabled by setting environment variable GRPC_EXPERIMENTAL_XDS_HTTP_CONNECT=true. (#9151)
• xds: Add support for contains_match in route header matchers. (#9223)

Bug Fixes

• credentials/alts: Fix panic when processing malformed frames by validating that the message frame length exceeds the message type field size. (#9197)
• grpc: Fix compilation on Plan 9 targets (GOOS=plan9), broken since v1.81.0. (#9255)
  • Special Thanks: @​Yusufihsangorgel

Commits

• 4c226da Change version to 1.83.0 (#9228)
• c198988 Cherrypick 9223 into v1.83.x (#9279)
• 8ce3ebf Cherrypick PR 9255 into v1.83.x (#9263)
• e393849 Cherry-pick recent changes from master (#9240)
• 2a112a8 authz: add onPolicyUpdate callback to authz file watcher (#9142)
• 1a80fca vet: adds a check to disallow usage of regex.Compile in xDS code (#9216)
• 26ffdb3 [tls] Add safety check in custom cert verification that peer cert chain is no...
• 5013974 internal/grpcsync: add ScheduleAndWait to CallbackSerializer (#9162)
• bd58bc0 internal/transport: increase test timeout locally in TestAccountCheckWindowSi...
• 484f150 httpfilter/extproc: add check to ensure that response trailer mode must be SE...
• Additional commits viewable in compare view

Updates gorm.io/driver/postgres from 1.6.0 to 1.6.2

Commits

• e269d69 Fix/preserve original error in translate (#335)
• 35fa84d chore(deps): bump actions/setup-go from 5 to 7 (#347)
• 6e6c866 feat: support PostgreSQL generated columns via the generated tag (#345)
• d9b9fc6 chore(deps): bump gorm.io/gorm from 1.25.10 to 1.31.2 (#346)
• 77dd2bd chore(deps): bump actions/checkout from 4 to 7 (#344)
• 2a16690 Refactor SQL query for column type retrieval (#343)
• ce8a605 chore(deps): bump github.com/jackc/pgx/v5 from 5.9.2 to 5.10.0 (#341)
• 4d6a58d fix(Migrator): add schema qualification to GetIndexes, RenameIndex, DropIndex...
• 65c4b89 fix(Migrator): prevent nil pointer dereference in AlterColumn (#339)
• 92d2b78 chore(deps): bump github.com/jackc/pgx/v5 from 5.8.0 to 5.9.2 (#337)
• Additional commits viewable in compare view

Updates gorm.io/driver/sqlserver from 1.6.3 to 1.6.4

Commits

• 50ac986 feat: support generated (computed) columns via the generated tag (#178)
• 8af2ff5 build(deps): bump actions/checkout from 6 to 7 (#179)
• c6fcffe build(deps): bump gorm.io/gorm from 1.30.0 to 1.31.2 (#181)
• de957b7 build(deps): bump golang.org/x/crypto from 0.45.0 to 0.52.0 (#182)
• c8ef2bf build(deps): bump actions/setup-go from 5 to 7 (#183)
• 6ca13a5 fix: schema-qualified table handling in SQL Server (#184)
• 05e6495 build(deps): bump actions/checkout from 4 to 6 (#174)
• 9971ad0 build(deps): bump github.com/microsoft/go-mssqldb from 1.8.2 to 1.9.6 (#176)
• fc75edd fix: The HasConstraint is fixed by adding a Unique Check (#173)
• See full diff in compare view

Updates modernc.org/sqlite from 1.54.0 to 1.56.0

Changelog

Sourced from modernc.org/sqlite's changelog.

Changelog

• 2026-08-09 v1.57.0:

  • Add an opt-in _defensive DSN query parameter that turns on SQLite's defensive mode for the connection, disabling the SQL-level features that let ordinary statements deliberately corrupt the database file. When _defensive=1 (or any strconv.ParseBool true value) is supplied, the driver calls sqlite3_db_config with SQLITE_DBCONFIG_DEFENSIVE immediately after sqlite3_open_v2 and before every other parameter is applied, so the PRAGMAs the driver itself runs, the _pragma list, and every statement the caller prepares are all subject to it. On such a connection PRAGMA writable_schema=ON, PRAGMA journal_mode=OFF and PRAGMA schema_version=N become silent no-ops, and writes to a virtual table's shadow tables (fts5's _data, _idx and so on) and to sqlite_dbpage fail with "table ... may not be modified"; reading those tables, ordinary use of the virtual tables that own them, and VACUUM are unaffected. The flag has no PRAGMA equivalent, so sqlite3_db_config — and therefore a DSN parameter — is the only way to reach it short of dropping to modernc.org/sqlite/lib. The value is parsed before sqlite3_open_v2, so an invalid one fails the connection without creating the database file, and the parameter must appear at most once: a repeated _defensive is an error rather than letting the first value silently win. Absence of the parameter, or _defensive=0, leaves SQLite's default behavior unchanged; existing DSNs continue to work byte-for-byte. Two limits are worth stating plainly, since the name invites more confidence than the flag earns. Defensive mode is a hardening measure, not a sandbox for hostile database files: it is one of several steps SQLite recommends for that purpose, and this build compiles with neither SQLITE_TRUSTED_SCHEMA=0 nor SQLITE_DQS=0 and exposes no authorizer. And it is a property of the connection, not of the database file — a second handle opened on the same file without the parameter is unrestricted.
  • Reject the one DSN combination defensive mode would otherwise swallow in silence. _defensive=1 together with _journal_mode=OFF (or _journal=OFF) now fails the connection instead of opening one in which neither parameter was honoured: SQLite turns PRAGMA journal_mode=OFF into a no-op that still reports success, so the driver would have accepted the mode, executed it, and left the journal untouched without telling anyone. The check runs in the validation phase introduced in v1.55.0, before any statement executes, so a rejected DSN cannot leave the database half-configured. _pragma remains the exception it has always been: _pragma=journal_mode(OFF) alongside _defensive=1 still runs and is still silently ignored by SQLite. Only DSNs using _defensive can be affected, and that parameter is new, so no DSN that opened before changes behavior.
  • See [GitHub pull request #6](modernc-org/sqlite#6), thanks wsman!

• 2026-08-03 v1.56.0:

  • Re-vendor the transpiled SQLite sources, picking up modernc.org/libsqlite3's fix for an upstream data-corruption bug in SQLite 3.53.3's journal rollback. The SQLite version is unchanged at 3.53.3; what changes is that the amalgamation is now patched before it is transpiled. 3.53.3 reworked readSuperJournal() to return the super-journal name through a char** out-parameter, and pager_playback() now tests that pointer where it used to test zSuper[0]. A crash during the commit of a multi-database (ATTACH) transaction can leave the super-journal name and its checksum zeroed while the name length and the trailing magic survive; the checksum is a plain byte sum, so an all-zero name still validates and readSuperJournal() hands back a non-NULL pointer to an empty string. pager_playback() then calls sqlite3OsAccess(pVfs, "", SQLITE_ACCESS_EXISTS), gets ENOENT, and deletes the hot journal without playing it back — leaving the database corrupted. This is not a transpilation artifact: a plain gcc build of the stock 3.53.3 amalgamation fails on the same bytes while 3.53.2 recovers them, and it is what has been making upstream's own test/crash.test fail intermittently, in roughly 2% of runs, on every platform. The patch restores the pre-3.53.3 behaviour of reporting a (nul) super-journal name and will be dropped once upstream ships its own fix. Every supported target carries it.
  • Two targets change beyond that patch. On linux/s390x the regenerated transpile allocates C bit-fields MSB-first, as the big-endian platform ABI requires, rather than LSB-first; this comes from modernc.org/cc/v4 v4.29.1 and touches bit-field accesses throughout the SQLite core, s390x being this module's only big-endian target. On linux/riscv64 the transpile was regenerated on a host running GCC 11.4.0 where the previous one used GCC 13.3.0, which drops a handful of unexported compiler-predefined macro constants (the __FLT16_* family, __DBL_IS_IEC_60559__ and friends) and changes the COMPILER=gcc-13.3.0 entry PRAGMA compile_options reports to COMPILER=gcc-11.4.0; no SQLite code generation differs. Every other target's generated code is byte-identical to v1.55.0 apart from the journal-rollback patch above.
  • Bump the pinned modernc.org/libc to v1.74.4, and the remaining dependencies to their current releases. v1.74.2 and v1.74.3 are retracted upstream — a freeaddrinfo lock leak that deadlocks name resolution — and v1.74.4 is the fix. As always, downstream modules must pin the exact modernc.org/libc version this module's go.mod pins (see [GitLab issue #177](https://gitlab.com/cznic/sqlite/-/issues/177)).
  • Documentation sweep. openbsd/amd64 and openbsd/arm64 join the supported platforms table in the package documentation: both have been in the builder test matrix since January and are cross-built by make build_all_targets, but had never been listed. The vfs DSN query parameter — which names a VFS registered with SQLite, such as one returned by vfs.New — is now documented alongside the other DSN parameters on Driver.Open. The "Debug and development versions" section no longer describes a GO_GENERATE environment variable and a go generate that this repository has not had since generator.go moved to modernc.org/libsqlite3; it now points at that repository and make vendor instead, and the stale //go:generate directive naming the removed file is dropped with it. modernc.org/sqlite/vec and modernc.org/sqlite/vfs gained the package doc comments they were missing, so both finally carry a synopsis on pkg.go.dev. Documentation only; no behavior changes.
  • Add NewConnector, returning a database/sql/driver.Connector for use with sql.OpenDB. It opens the same connections sql.Open("sqlite", dsn) does, from the same registered driver, so every function, collation, connection hook and virtual table module registered through this package applies to them. It exists for callers that need to interpose on the physical connections database/sql opens — tracing, metrics, connection-scoped setup — which sql.Open gives no access to: such a caller can embed the returned Connector, override Connect, and pass its own wrapper to sql.OpenDB. Previously the only way to reach the registered driver was the db, _ := sql.Open("sqlite", ""); drv := db.Driver(); db.Close() idiom, which works only because sql.Open does not connect and this driver does not implement driver.DriverContext; and the only way to get a wrapper into a *sql.DB was sql.Register, which is process-global, panics on a name it has already seen, and cannot be undone, so a library had to invent a unique driver name per configuration. sql.OpenDB registers nothing. Constructing a &sqlite.Driver{} is not an alternative — its fields are unexported, so it carries none of the registrations. NewConnector checks the DSN only as far as it can without opening a database — a query string that does not parse, and conflicting vfs parameters; everything else continues to be validated when the connection is opened, so an unknown parameter or an out-of-range value is reported by Connect rather than at construction. Nothing about the existing sql.Open path changes: *Driver deliberately still does not implement driver.DriverContext, so sql.Open remains lazy and DSN errors continue to surface where they always have. A runnable sample is in examples/connector. Resolves [GitLab issue #253](https://gitlab.com/cznic/sqlite/-/issues/253), thanks Alessandro Segala (@​ItalyPaleAle)!
  • Document that a caller-constructed sqlite.Driver is not the driver this package registers as "sqlite". Its fields are unexported, so it starts with no functions, collations or connection hooks and the only way to give it any is its own RegisterConnectionHook method; the package-level Register* functions always apply to the registered driver. Connections such a Driver opens therefore run without the package-level functions and collations — and because a registered function silently replaces a SQLite built-in of the same name, a Driver you construct can evaluate upper(x), date(x) and the like differently from one opened through sql.Open. Virtual table modules are the one exception: they are held process-globally and reach every Driver. Constructing one remains supported for the private-hook pattern — a driver registered under a name of its own with sql.Register so its connection hooks apply only to its own connections — and is otherwise best avoided in favour of sql.Open or NewConnector. Documentation only; no behavior changes.

• 2026-07-20 v1.55.0:

  • Add github.com/mattn/go-sqlite3-compatible shorthand DSN query parameters to ease migration from that driver: _busy_timeout/_timeout, _foreign_keys/_fk, _journal_mode/_journal, _synchronous/_sync, _auto_vacuum/_vacuum, and _query_only, each setting the correspondingly named PRAGMA. Values are validated against the same set mattn/go-sqlite3 accepts (case-insensitive) and an unrecognized value fails the connection with an error, so a typo such as _synchronous=fu1l or _foreign_keys=yes_please is reported rather than silently downgrading durability or dropping foreign-key enforcement. The keys are applied in a fixed order independent of their order in the DSN — _busy_timeout and _auto_vacuum before any _pragma values (auto_vacuum must be set before the database is first written), the rest after, and _query_only last — and where a key and its alias are both supplied the alias wins, matching mattn/...

    Description has been truncated