Skip to content

build(deps): bump the go group with 3 updates - #30

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/go-a508452155
Open

build(deps): bump the go group with 3 updates#30
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/go-a508452155

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 8, 2026

Copy link
Copy Markdown
Contributor

Bumps the go group with 3 updates: github.com/Microsoft/go-winio, go.yaml.in/yaml/v4 and modernc.org/sqlite.

Updates github.com/Microsoft/go-winio from 0.6.2 to 0.6.4

Release notes

Sourced from github.com/Microsoft/go-winio's releases.

v0.6.4

What's Changed

Full Changelog: microsoft/go-winio@v0.6.3...v0.6.4

v0.6.3

What's Changed

New Contributors

Full Changelog: microsoft/go-winio@v0.6.2...v0.6.3

Commits
  • b900fd8 Fix regression in mkwinsyscall for non SystemDLLs (#394)
  • 48c993a Bump golang.org/x/sys from 0.48.0 to 0.49.0 (#393)
  • 2430248 improve interoperability with stdlib sentinel errors and deprecate aliases (#...
  • f19d971 linting: enable dupword, intrange, mirror, gocritic (#387)
  • 0b70f54 tools/mkwinsyscall: remove errnoERROR_IO_PENDING const (#260)
  • 7e8af9b Resolves race in makeConnectedServerPipe / Close (#388)
  • 70234f2 Bump golang.org/x/tools to v0.50.0 (#385)
  • 1de8712 fix linting issues (#325)
  • 3093527 ci: update actions and golangci-lint, and fix linting (#349)
  • c7e589d Merge pull request #383 from thaJeztah/use_tool_generate
  • Additional commits viewable in compare view

Updates go.yaml.in/yaml/v4 from 4.0.0-rc.6 to 4.0.0

Release notes

Sourced from go.yaml.in/yaml/v4's releases.

go-yaml v4.0.0

go-yaml v4.0.0 is the first stable release of the v4 series, maintained by the YAML organization. It adds configurable loading and dumping, public plugin interfaces, structured errors, and a CLI for inspecting YAML processing. The classic APIs remain supported, so applications can adopt v4 incrementally.

Getting started

Install the release:

go get go.yaml.in/yaml/v4@v4.0.0

Use this import path in your Go code:

import "go.yaml.in/yaml/v4"

For an existing v3 application, start by updating imports, reviewing custom unmarshalers, and running your tests. You can continue using Unmarshal, Marshal, NewDecoder, and NewEncoder. The v2 and v3 APIs remain frozen, with security fixes only; new features and routine bug fixes are developed in v4.

Why add Load and Dump?

Applications need different YAML policies: strict configuration validation, particular output layouts, or custom anchor handling. The new Load and Dump functions and streaming Loader and Dumper accept functional options and plugins for those choices. They use YAML's load/dump terminology and are recommended for new code.

The classic entry points keep compatibility settings rather than changing formatting and error presentation for every existing caller. Moving to the new API is an explicit choice to use v4 defaults, with presets available when you want older settings. Classic APIs remain supported.

For example, load a configuration with strict field checking, then choose its output indentation:

package main
import (
"fmt"
</tr></table>

... (truncated)

Commits
  • f2f9563 Add a target for GitHub release drafts
  • f154859 Add release notes for go-yaml v4.0.0
  • dcd0fa5 Prepare documentation for the v4 release
  • abc9fb0 Remove deprecated Limit plugin API
  • 3fefab0 Compare YTS JSON numbers as float64
  • 2141fcc Restore default limits for Node.Decode
  • 57eefb4 Document legacy encoder indentation behavior
  • 2dc529e Restore dead-code elimination in error formatting
  • 2ac821e Bump the actions group with 3 updates
  • 24e7908 Fix Alias-Data review findings
  • Additional commits viewable in compare view

Updates modernc.org/sqlite from 1.61.0 to 1.61.1

Release notes

Sourced from modernc.org/sqlite's releases.

v1.61.1

Signed provenance for this release: the two files below. VERIFYING.md in the repository says how to check them.

Changelog

Sourced from modernc.org/sqlite's changelog.

Changelog

Entries for v1.38.1 through v1.44.1 and for v1.49.1 were added on 2026-09-05, reconstructed from the git history and the merge requests they cite; they were missing at release time.

  • 2026-11-07 v1.62.0:

    • Add illumos/amd64, tested on an OmniOS builder. Resolves [GitLab issue #210](https://gitlab.com/cznic/sqlite/-/issues/210), thanks Jasper Siepkes (@​siepkes), who also started the modernc.org/libc port!
    • Re-vendor lib/ from modernc.org/libsqlite3 v1.16.0 and vec/ from modernc.org/libsqlite_vec v0.8.0; SQLite stays 3.54.1 and sqlite-vec v0.1.9. The pinned modernc.org/libc becomes v1.80.1; as always, downstream go.mod files must pin the same modernc.org/libc version this repository's go.mod does, see [GitLab issue #177](https://gitlab.com/cznic/sqlite/-/issues/177).
    • Add opt-in syncing with fdatasync(2), off by default: Fdatasync(true) makes commits sync with fdatasync instead of fsync, process-wide, which skips the timestamp update fsync forces and keeps a commit just as durable. FdatasyncEnabled reports the setting; on macOS and Windows Fdatasync returns ErrFdatasyncUnavailable. Resolves [GitHub issue #10](modernc-org/sqlite#10), thanks aibeshkov!
    • Limit now works on a connection handed out by a driver.Connector that wraps the ones NewConnector opens, provided the wrapper has an Unwrap() driver.Conn method; it used to fail with unexpected driverConn type. NewConnector now also says which optional interfaces such a wrapper must forward. Resolves [GitHub issue #11](modernc-org/sqlite#11), thanks Andres Morey (@​amorey)!

  • 2026-10-31 v1.61.1:

    • Prepared statements are no longer parsed and planned again on every execution. Since v1.61.0, SQLite 3.54 expired a cached statement that has a col = ? term in a join or an ORDER BY query whenever the driver cleared its bindings after a run, so a statement prepared with db.Prepare or tx.Prepare cost about twice what it did in v1.60.1. Integer bindings now stay in place between executions, so a parameter bound to 0 or 1 does not re-prepare it either. Resolves [GitLab issue #264](https://gitlab.com/cznic/sqlite/-/issues/264). See [GitLab merge request #147](https://gitlab.com/cznic/sqlite/-/merge_requests/147), thanks Roman Khafizianov (@​requilence)!
    • Fix a panic reachable from SQL through a VFS made by vfs.New. It reported its files as writable, so with PRAGMA journal_mode=OFF a write reached a write method the VFS does not have and the process panicked, as did closing a WAL database shipped with its -wal file; with the journal on, the write failed with a misleading SQLITE_NOMEM. Such files are now read-only to SQLite, and every write fails with SQLITE_READONLY. See [GitLab merge request #145](https://gitlab.com/cznic/sqlite/-/merge_requests/145), thanks Ian Chechin!
    • Fix a process abort reachable through a VFS made by vfs.New. SQLite's request to delete a journal, made when PRAGMA journal_mode leaves PERSIST or TRUNCATE and on the first read of a 0-byte database that has a -journal file next to it in the served file system, reached the transpiled xDelete, an unimplemented stub that aborted the process. It now fails with SQLITE_IOERR_DELETE, which SQLite tolerates, and nothing is deleted; the write methods the VFS lacked answer SQLITE_READONLY instead of being nil.
    • Tx.Commit now stops waiting for a lock once the context given to BeginTx is done, and Rows.Next and Rows.Close once the query's context is done, each returning the context's error; they used to wait the full busy_timeout when a reader's lock in rollback-journal mode blocked the COMMIT, or the commit of an autocommit INSERT ... RETURNING finished or closed after its first row. Only the wait watches the context; Rollback is unchanged. Resolves [GitLab issue #263](https://gitlab.com/cznic/sqlite/-/issues/263), thanks SirLouen!
    • The attest CI job now copies vendor.json into the provenance document from the tagged commit, not from the working tree make vendor-check has just stamped with its own Go release; the v1.61.0 job failed its own verification over that field, so v1.61.0 has no provenance document, see VERIFYING.md. Tooling only.
    • Add THREAT-MODEL.md, the threat model behind the scope in SECURITY.md: the connection string, the connection lifecycle, the page cache binding and the VFS bridge, one row per concern with its status and the commit that settled it. TestVFSReadEOF now also checks the short read on vfsRead itself. Documentation and tests only. See [GitLab merge request #146](https://gitlab.com/cznic/sqlite/-/merge_requests/146), thanks Ian Chechin!

  • 2026-10-21 v1.61.0:

  • 2026-09-29 v1.60.1:

    • Binding arguments to a statement is no longer quadratic in the number of its parameters, which made multi-row INSERTs with thousands of ? parameters slow. Resolves [GitHub issue #8](modernc-org/sqlite#8), thanks wencycool!

  • 2026-09-28 v1.60.0:

    • A fault while reading the memory-mapped -shm file of a WAL database no longer crashes the process. The statement fails with a disk I/O error, extended code SQLITE_IOERR_IN_PAGE (8714), and the connection stays usable, as in MSVC builds of SQLite. On by default on every platform and not switchable; lib.SehInject and lib.SehPending inject such a fault for tests. Resolves [GitLab issue #221](https://gitlab.com/cznic/sqlite/-/issues/221), thanks Roman (@​requilence) for the report, and supersedes libsqlite3!4 and [GitHub pull request #7](modernc-org/sqlite#7), thanks hazyhaar for the two rounds, the ccgo finding and the Windows Server runs!
    • Re-vendor lib/ from modernc.org/libsqlite3 v1.15.0 and vec/ from modernc.org/libsqlite_vec v0.6.0; SQLite stays 3.53.4 and sqlite-vec v0.1.9. Go 1.26 is now required, and the pinned modernc.org/libc becomes v1.77.1; as always, downstream go.mod files must pin the same modernc.org/libc version this repository's go.mod does, see [GitLab issue #177](https://gitlab.com/cznic/sqlite/-/issues/177).
    • Nine exported lib constants that never had a meaningful value are gone: INFINITY, MB_CUR_MAX, NAN, RESERVED_BYTE, SHARED_FIRST, SQLITE_CANTOPEN_BKPT, SQLITE_CORRUPT_BKPT, SQLITE_DEFAULT_LOOKASIDE and SQLITE_MISUSE_BKPT. The transpiler now evaluates object-like macros as C expressions, so other constants take their C value (lib.WALINDEX_PGSZ is 32768, not 0) and some appear; the full list is in libsqlite3's CHANGELOG under 2026-09-19.
    • make vendor now writes vendor.json, the modernc.org/libsqlite3 and modernc.org/libsqlite_vec commits and the Go toolchain lib/ and vec/ were vendored with, so git show vX.Y.Z:vendor.json says which revisions a release carries; the test suite fails when they no longer match. Tooling only. See [GitLab merge request #140](https://gitlab.com/cznic/sqlite/-/merge_requests/140).
    • vfs.FS.Close now refuses while a database opened through it is still open, returning an error that wraps the new vfs.ErrInUse and leaving the VFS registered. It used to free the VFS the open connection still called through, so the next query crashed the process or read through freed memory. Close the databases first, then the FS.
    • Fix handle reuse in modernc.org/sqlite/vfs on 32-bit targets: after 2^32 file opens in one process the handle counter wrapped and could overwrite a live entry, such as a file system registered at start-up, and crash. 64-bit targets were not affected.
    • The pluggable page cache now panics when a Cache breaks its contract by returning nil, or a different Page, from Fetch for a page SQLite still holds pinned. It used to free memory SQLite was still using, corrupting the database without an error. Only a Cache implementation with that bug is affected; modernc.org/sqlite/pcache is not.
    • Document three limits of the pluggable page cache on RegisterPageCache and Cache: it cannot be combined with modernc.org/sqlite/vec, PageCache.Create may be called concurrently, and under cache=shared a Cache is called from several goroutines. Documentation only.
    • Document in the package documentation that state set on a pooled connection is inherited by the next caller to borrow it, and that a connection reached through sql.Conn.Raw is not safe for concurrent use. Documentation only.
    • Add StrictPragmas, opt-in and off by default: once enabled, a connection whose _pragma DSN value holds more than one SQL statement fails to open with ErrMultiStatementPragma, before any DSN parameter is applied. A _pragma value runs as SQL text, so anything after a ; runs too. Recommended for any application whose DSN is not a compile-time constant.
    • Document SQLite's own URI query parameters on Driver.Open: mode, cache, immutable, nolock, psow and modeof, which have always worked in a DSN starting with file:, and the trap that a plain file name has its query stripped before SQLite sees it, so /path/to.db?mode=ro opens read-write. Resolves [GitLab issue #257](https://gitlab.com/cznic/sqlite/-/issues/257). Documentation only.
    • Add SECURITY.md, the vulnerability reporting policy: three private channels, what is in scope, that only the latest release is supported, and how a confirmed report is disclosed, including an entry in the Go vulnerability database so govulncheck reports it. IRP.md, linked from it, is the maintainers' incident response plan. Documentation only.
    • Add CONTRIBUTING.md: where to send a merge request, which files are generated and must not be edited by hand, how to build and test across the 20 supported targets, and the AUTHORS/CONTRIBUTORS convention. Documentation only.
    • Ship LICENSE-3RD-PARTY.md, a transitively flattened inventory of every third-party component this module carries with all seventeen license texts in full, and a Software Bill of Materials, sbom.cdx.json (CycloneDX 1.6) and sbom.spdx.json (SPDX 2.3), explained in SBOM.md. Both cover what a module-graph tool cannot see: the transpiled SQLite and sqlite-vec C, and the upstreams modernc.org/libc carries, musl among them. Documentation only.

  • 2026-09-15 v1.59.0:

    • Bump the pinned modernc.org/libc to v1.75.7 and re-vendor lib/ and vec/. The transpiled SQLite is unchanged, still 3.53.4. On the Linux targets the new libc replaces transpiled musl memcpy, memmove, memset, memcmp and strlen with native Go, cutting CPU time on query-heavy workloads by up to a third; see the new Performance section below. As always, downstream go.mod files must pin the same modernc.org/libc version this repository's go.mod does; see [GitLab issue #177](https://gitlab.com/cznic/sqlite/-/issues/177).

... (truncated)

Commits
  • 014351f CHANGELOG.md: v1.61.1
  • e699042 conn.go, stmt.go, rows.go: unbind only the parameters that point into the dri...
  • 519e1d2 Merge branch 'clear-bindings-reprepare' into 'master'
  • 0afd2c8 stmt.go, reprepare_test.go, AUTHORS, CONTRIBUTORS: stop re-preparing cached s...
  • 683b727 vfs: implement xDelete and the write methods SQLite could still reach
  • 78c3b0c Merge branch 'threat-model' into 'master'
  • 56d8077 Merge branch 'vfs-readonly-open' into 'master'
  • 0ea9fb8 THREAT-MODEL.md: a row for the vfs.New write panic
  • 67055eb CHANGELOG.md: the vfs.New write panic
  • bbce27d CHANGELOG.md: the threat model and the short-read assertion
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
build(deps): bump the go group with 3 updates
b7e790c 
Bumps the go group with 3 updates: [github.com/Microsoft/go-winio](https://github.com/Microsoft/go-winio), [go.yaml.in/yaml/v4](https://github.com/yaml/go-yaml) and [modernc.org/sqlite](https://gitlab.com/cznic/sqlite).


Updates `github.com/Microsoft/go-winio` from 0.6.2 to 0.6.4
- [Release notes](https://github.com/Microsoft/go-winio/releases)
- [Commits](microsoft/go-winio@v0.6.2...v0.6.4)

Updates `go.yaml.in/yaml/v4` from 4.0.0-rc.6 to 4.0.0
- [Release notes](https://github.com/yaml/go-yaml/releases)
- [Commits](yaml/go-yaml@v4.0.0-rc.6...v4.0.0)

Updates `modernc.org/sqlite` from 1.61.0 to 1.61.1
- [Release notes](https://gitlab.com/cznic/sqlite/tags)
- [Changelog](https://gitlab.com/cznic/sqlite/blob/master/CHANGELOG.md)
- [Commits](https://gitlab.com/cznic/sqlite/compare/v1.61.0...v1.61.1)

---
updated-dependencies:
- dependency-name: github.com/Microsoft/go-winio
  dependency-version: 0.6.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go
- dependency-name: go.yaml.in/yaml/v4
  dependency-version: 4.0.0
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go
- dependency-name: modernc.org/sqlite
  dependency-version: 1.61.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Nov 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants