build(deps): bump github.com/ncruces/go-sqlite3 from 0.32.0 to 0.33.3 in the production-dependencies group

[dependabot]

Bumps the production-dependencies group with 1 update: github.com/ncruces/go-sqlite3.

Updates github.com/ncruces/go-sqlite3 from 0.32.0 to 0.33.3

Release notes

Sourced from github.com/ncruces/go-sqlite3's releases.

v0.33.3

[!IMPORTANT]

This is one of the first versions of this package to use wasm2go.

wasm2go is a recent project, so you may prefer to stick to previous versions, if you value stability.

Your feedback on this change is very appreciated. Please read and comment on the discussion.

What's Changed

Updates:

• SQLite 3.53.0

Full Changelog: ncruces/go-sqlite3@v0.33.2...v0.33.3

Artifact attestations

v0.33.2

[!IMPORTANT]

This is one of the first versions of this package to use wasm2go.

wasm2go is a recent project, so you may prefer to stick to previous versions, if you value stability.

wasm2go had a bug affecting the following GOARCHs: alpha, arm, mipsle, mips64le, riscv, riscv64, sh. If you have users using these CPUs, please upgrade SQLite to v0.33.2.

Your feedback on this change is very appreciated. Please read and comment on the discussion.

This is a breaking change, but in most cases, upgrading is as simple as removing this import from your code:

import _ "github.com/ncruces/go-sqlite3/embed"

If you were configuring how much memory you gave your SQLite connections, you need to:

// Stop doing this:
sqlite3.RuntimeConfig = wazero.NewRuntimeConfig().WithMemoryLimitPages(512) // 32 MB
// And use this context to open your connections:
sqliteCtx := sqlite3.WithMaxMemory(parentCtx, 3210241024) // 32 MB

Full Changelog: ncruces/go-sqlite3@v0.32.0...v0.33.2

Commits

• 02af344 SQLite 3.53.0.
• 61d2c85 CI.
• 7daf908 Portable.
• 13edc95 Regen.
• b6e44cc Regen.
• 2c6806e Regen.
• 361fdc5 SQLite 3.51.3.
• 1008ddc JSON.
• 1956c5a Cleanup.
• 1165211 Switch from wazero to wasm2go (#362)
• See full diff 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