Skip to content

chore(deps): bump the go-modules group with 14 updates - #333

Merged
paketo-bot merged 1 commit into
mainfrom
dependabot/go_modules/go-modules-4970b5b3c3
Sep 4, 2026
Merged

chore(deps): bump the go-modules group with 14 updates#333
paketo-bot merged 1 commit into
mainfrom
dependabot/go_modules/go-modules-4970b5b3c3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 4, 2026

Copy link
Copy Markdown
Contributor

Bumps the go-modules group with 14 updates:

Package From To
github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp 1.36.0 1.37.0
github.com/GoogleCloudPlatform/opentelemetry-operations-go/exporter/metric 0.60.0 0.61.0
github.com/GoogleCloudPlatform/opentelemetry-operations-go/internal/resourcemapping 0.60.0 0.61.0
github.com/aws/aws-sdk-go-v2/config 1.33.1 1.33.2
github.com/aws/aws-sdk-go-v2/credentials 1.20.1 1.20.2
github.com/aws/aws-sdk-go-v2/service/s3 1.109.1 1.110.0
github.com/aws/aws-sdk-go-v2/service/signin 1.7.1 1.8.0
github.com/aws/aws-sdk-go-v2/service/sso 1.35.1 1.36.0
github.com/aws/aws-sdk-go-v2/service/ssooidc 1.40.1 1.41.0
github.com/aws/aws-sdk-go-v2/service/sts 1.47.1 1.48.0
github.com/ebitengine/purego 0.10.2 0.11.0
github.com/gpustack/gguf-parser-go 0.26.2 0.26.3
google.golang.org/api 0.295.0 0.296.0
modernc.org/sqlite 1.57.0 1.58.0

Updates github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp from 1.36.0 to 1.37.0

Commits
  • 8b7faf9 Prepare release v1.37.0/v0.61.0 (#1198)
  • a947a67 detectors/gcp: deprecate GCP resource detection package (#1193)
  • 8e4e169 propagator: deprecate package and add missing module-level deprecations (#1196)
  • 4451cb5 cloudbuild: update Cloud Functions gen2 e2e test runtime to go126 (#1195)
  • 997ea47 Deprecate extension/googleclientauthextension module (#1187)
  • 94c348e Deprecate trace and metric exporters and add migration guide (#1192)
  • 74a3848 Drop support for go 1.25 (#1190)
  • See full diff in compare view

Updates github.com/GoogleCloudPlatform/opentelemetry-operations-go/exporter/metric from 0.60.0 to 0.61.0

Release notes

Sourced from github.com/GoogleCloudPlatform/opentelemetry-operations-go/exporter/metric's releases.

v1.37.0/v0.61.0

What's Changed

Full Changelog: GoogleCloudPlatform/opentelemetry-operations-go@v0.60.0...v0.61.0

Commits
  • 8b7faf9 Prepare release v1.37.0/v0.61.0 (#1198)
  • a947a67 detectors/gcp: deprecate GCP resource detection package (#1193)
  • 8e4e169 propagator: deprecate package and add missing module-level deprecations (#1196)
  • 4451cb5 cloudbuild: update Cloud Functions gen2 e2e test runtime to go126 (#1195)
  • 997ea47 Deprecate extension/googleclientauthextension module (#1187)
  • 94c348e Deprecate trace and metric exporters and add migration guide (#1192)
  • 74a3848 Drop support for go 1.25 (#1190)
  • See full diff in compare view

Updates github.com/GoogleCloudPlatform/opentelemetry-operations-go/internal/resourcemapping from 0.60.0 to 0.61.0

Release notes

Sourced from github.com/GoogleCloudPlatform/opentelemetry-operations-go/internal/resourcemapping's releases.

v1.37.0/v0.61.0

What's Changed

Full Changelog: GoogleCloudPlatform/opentelemetry-operations-go@v0.60.0...v0.61.0

Commits
  • 8b7faf9 Prepare release v1.37.0/v0.61.0 (#1198)
  • a947a67 detectors/gcp: deprecate GCP resource detection package (#1193)
  • 8e4e169 propagator: deprecate package and add missing module-level deprecations (#1196)
  • 4451cb5 cloudbuild: update Cloud Functions gen2 e2e test runtime to go126 (#1195)
  • 997ea47 Deprecate extension/googleclientauthextension module (#1187)
  • 94c348e Deprecate trace and metric exporters and add migration guide (#1192)
  • 74a3848 Drop support for go 1.25 (#1190)
  • See full diff in compare view

Updates github.com/aws/aws-sdk-go-v2/config from 1.33.1 to 1.33.2

Commits

Updates github.com/aws/aws-sdk-go-v2/credentials from 1.20.1 to 1.20.2

Commits

Updates github.com/aws/aws-sdk-go-v2/service/s3 from 1.109.1 to 1.110.0

Commits

Updates github.com/aws/aws-sdk-go-v2/service/signin from 1.7.1 to 1.8.0

Changelog

Sourced from github.com/aws/aws-sdk-go-v2/service/signin's changelog.

Release (2021-08-04)

General Highlights

  • Feature: adds error handling for defered close calls
  • Dependency Update: Updated github.com/aws/smithy-go to latest version.
  • Dependency Update: Updated to the latest SDK module versions

Module Highlights

  • github.com/aws/aws-sdk-go-v2: v1.8.0
    • Bug Fix: Corrected an issue where the retryer was not using the last attempt's ResultMetadata as the bases for the return result from the stack. (#1345)
  • github.com/aws/aws-sdk-go-v2/feature/dynamodb/expression: v1.2.0
    • Feature: Add IsSet helper for ConditionBuilder and KeyConditionBuilder (#1329)
  • github.com/aws/aws-sdk-go-v2/service/accessanalyzer: v1.5.2
    • Bug Fix: Fixed an issue that caused one or more API operations to fail when attempting to resolve the service endpoint. (#1349)
  • github.com/aws/aws-sdk-go-v2/service/amp: v1.3.1
    • Bug Fix: Fixed an issue that caused one or more API operations to fail when attempting to resolve the service endpoint. (#1349)
  • github.com/aws/aws-sdk-go-v2/service/appintegrations: v1.5.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/appmesh: v1.4.2
    • Bug Fix: Fixed an issue that caused one or more API operations to fail when attempting to resolve the service endpoint. (#1349)
  • github.com/aws/aws-sdk-go-v2/service/appsync: v1.5.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/auditmanager: v1.7.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/batch: v1.6.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/braket: v1.5.2
    • Bug Fix: Fixed an issue that caused one or more API operations to fail when attempting to resolve the service endpoint. (#1349)
  • github.com/aws/aws-sdk-go-v2/service/chime: v1.7.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/cloudformation: v1.8.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/cloudwatch: v1.7.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/codebuild: v1.6.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/codeguruprofiler: v1.4.2
    • Bug Fix: Fixed an issue that caused one or more API operations to fail when attempting to resolve the service endpoint. (#1349)
  • github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider: v1.5.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/computeoptimizer: v1.7.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/databrew: v1.7.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/directconnect: v1.7.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/ec2: v1.13.0
    • Feature: Updated to latest API model.
  • github.com/aws/aws-sdk-go-v2/service/ecs: v1.7.0
    • Feature: Updated to latest API model.

... (truncated)

Commits

Updates github.com/aws/aws-sdk-go-v2/service/sso from 1.35.1 to 1.36.0

Commits

Updates github.com/aws/aws-sdk-go-v2/service/ssooidc from 1.40.1 to 1.41.0

Commits

Updates github.com/aws/aws-sdk-go-v2/service/sts from 1.47.1 to 1.48.0

Commits

Updates github.com/ebitengine/purego from 0.10.2 to 0.11.0

Release notes

Sourced from github.com/ebitengine/purego's releases.

v0.11.0

  • Require Go 1.25 or later (#469)
  • Support structs on Windows amd64/arm64, Android, iOS, loong64, and ppc64le (#237, #466, #473, #475)
  • Support structs as arguments and return values in callbacks (#225, #418)
  • Add NetBSD (amd64, arm64) as a Tier 2 platform (#349)
  • Support the ARM soft-float ABI (#490)
  • Support linux/s390x without Cgo (#422)
  • Support up to 32 arguments on 64-bit platforms (#425)
  • Add cstrings.NSStringToString (#438)
  • Fix some bugs
Commits
  • 11ec78d all: v0.11.0 released
  • 63002e0 purego: apply go fix modernizations (#504)
  • f389379 all: use range-over-int in counting loops (#503)
  • 749871c all: use structs.HostLayout on structs that must match the C ABI (#502)
  • a66c0b0 purego: fix returning a C function pointer as a Go func (#500)
  • f2f4202 objc: encode 64-bit integers as q and Q (#499)
  • 7d5f4c2 .github/workflows: test against Go 1.27 (#498)
  • f9d41fc purego: support arm soft-float abi (#494)
  • 0960e99 all: remove zcallback_*.s from the external code list (#496)
  • 4862512 .github/workflows: test against 1.27-rc2 (#495)
  • Additional commits viewable in compare view

Updates github.com/gpustack/gguf-parser-go from 0.26.2 to 0.26.3

Commits
  • e11f991 ci: configure project review rules for open-code-review
  • 96a7a9c ci: introduce AI code review workflow and agent onboarding docs (#55)
  • 8ce1632 fix: bound the declared array length in ReadArray before allocating
  • See full diff in compare view

Updates google.golang.org/api from 0.295.0 to 0.296.0

Release notes

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

v0.296.0

0.296.0 (2026-08-31)

Features

Changelog

Sourced from google.golang.org/api's changelog.

0.296.0 (2026-08-31)

Features

Commits

Updates modernc.org/sqlite from 1.57.0 to 1.58.0

Changelog

Sourced from modernc.org/sqlite's changelog.

Changelog

  • 2026-09-01 v1.58.0:

    • Upgrade to SQLite 3.53.4. Upstream's own fix for the journal-rollback data-corruption bug is part of this release, so the local super-journal patch v1.56.0 introduced — and promised to drop once upstream shipped theirs — is dropped; recovery behavior is unchanged. This also bumps the pinned modernc.org/libc to v1.75.6; 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)).
    • Add opt-in support for Linux Open File Description (OFD) locks on database files. A POSIX record lock is owned by the (process, inode) pair, so the kernel drops every lock the process holds on a database file whenever any descriptor of that file is closed: an os.Open/Close for a hash, a backup check or a metadata probe anywhere in the process — third-party libraries included — silently strips SQLite's transaction locks and leaves the file unprotected against other processes. With OFD locking enabled, the locks belong to the open file description that placed them and survive such a close. Off by default, and staying off until the mode has real-world mileage: without opting in, locking behavior is byte-for-byte that of previous releases. Enable it by setting MODERNC_SQLITE_OFD_LOCK=1 in the environment the process starts with (any value but the empty string or one starting with 0; read once, at library initialization), or from Go with the new OFDLocking(true), which overrides the variable and must run before the first connection is opened; OFDLockingEnabled reports the mode in effect. The switch is deliberately process-wide rather than a DSN parameter: POSIX and OFD locks taken by one process are different owners to the kernel and genuinely conflict, so every connection to a database file inside one process must use the same kind, and a per-DSN knob would advertise a granularity the kernel does not offer (see the discussion in #255). Because the two kinds do not release one another, the mode is frozen at the process's first lock attempt: later attempts to change it return the new ErrOFDLockingTooLate, while querying, and setting the value already in effect, keep working. On kernels older than 3.15, and on filesystems that reject OFD locks, the first lock attempt falls back to POSIX locks for good and OFDLocking returns the new ErrOFDLockingUnavailable from then on, which is also how OFDLockingEnabled turning false reports the fallback; the same error is returned on every platform but Linux, where the API exists but OFD locks do not. Two boundaries to note: the immunity covers the locks on the database file itself, while WAL's -shm coordination stays on POSIX locks; and code in the same process that takes fcntl record locks of its own on a database file — which used to never conflict with SQLite's, while quietly destroying them — now conflicts with them loudly instead. The C side — F_OFD_SETLK routing through a designated per-inode locking descriptor that preserves upstream's unixInodeInfo semantics (last-unlocker release, PENDING piggybacking, unix-excl), guarded to __linux__ — ships in the transpiled sources via libsqlite3!3 and its follow-up hardening, with the OFD lock constants from libc!33; the review rounds, the /proc/locks measurements behind the design, and the Tcl lock/WAL gate that runs both modes are recorded in [GitLab issue #255](https://gitlab.com/cznic/sqlite/-/issues/255) and those merge requests.
    • Add the accompanying regression tests. The four OFD scenarios contributed in merge request #136 — lock survival across a rogue os.Close, the interleaved-readers lock lifecycle, the read-only-first designated-descriptor migration, and the failed-first-lock cleanup — run in a re-executed child process with MODERNC_SQLITE_OFD_LOCK=1, since the mode is process-wide and frozen at the first lock so the suite's own process cannot switch; a positive control asserts the variable really switched the mode on before each scenario runs, and the two scenarios whose invariants hold under both modes also run in the parent process's inherited mode. TestOFDLockingSetter exercises the Go call path end to end in a clean child — off by default, enabled before the first connection, the kernel-visible OFDLCK record in /proc/locks as the positive control, frozen after the first lock — and on every other platform the switch is asserted to report itself unavailable.
    • Resolves [GitLab issue #255](https://gitlab.com/cznic/sqlite/-/issues/255). See [GitLab merge request #136](https://gitlab.com/cznic/sqlite/-/merge_requests/136), thanks @​technosloth, and thanks Gani Georgiev (@​ganigeorgiev) for pressing the opt-in default!

  • 2026-08-19 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!
    • Ship the sqlite-vec license notice this module has been missing. modernc.org/sqlite/vec has bundled the transpiled sqlite-vec sources since v1.47.0, but the module carried only its own BSD-3-Clause LICENSE and the public-domain SQLite notice. sqlite-vec is Copyright (c) 2024 Alex Garcia, dual-licensed Apache-2.0 OR MIT and used here under MIT, whose terms require the copyright and permission notice to accompany substantial portions of the software — which 2.8 MB of transpiled vec/ plainly is. The notice now ships as LICENSE-SQLITE_VEC in the module root, byte-identical to the LICENSE-MIT in the upstream v0.1.9 archive and named after the file modernc.org/libsqlite_vec extracts it into. Attribution was never absent — vec's package documentation has named the extension, pinned the version and linked upstream — but the license text itself was, and the omission was ours: vendor_libs/main.go copied the per-target transpiles and nothing else. It now copies the notice alongside them and fails the vendoring run if it cannot, so a make vendor can no longer quietly drop it. The vec package documentation gained a License section recording that the package is under a different license from the rest of this module.
    • The SQLite notice is renamed from SQLITE-LICENSE to LICENSE-SQLITE; update any direct links to it. Its contents are unchanged and SQLite remains public domain. The name now matches both the new LICENSE-SQLITE_VEC beside it and the LICENSE-<upstream> convention every other modernc.org repository follows, but it is more than cosmetic: go mod vendor selects the files it copies into a downstream vendor/ tree by matching each name against a fixed list of prefixes — LICENSE among them — so a name merely ending in LICENSE was never propagated. Both bundled notices now travel with the code into vendored builds, which is where the MIT terms on vec/ keep applying. No code changes; no behavior changes.
    • Let a caller-constructed Driver register its own functions, collations and virtual table modules. Driver has always held four categories of registration state, but only RegisterConnectionHook could put anything on a constructed one: functions and collations were reachable through the package-level API alone, and modules through the package-level driver only, which left the modules field written and read through that instance and so process-global state wearing a per-instance field. Driver now has RegisterFunction, RegisterScalarFunction, RegisterDeterministicScalarFunction, RegisterCollationUtf8 and RegisterModule, plus Must* variants of the first four, each registering on that Driver alone; the methods are safe to call concurrently, and the zero Driver is ready to use as-is. vtab.RegisterModule also honours its db argument now: a non-nil db registers on the driver backing it when that driver implements the new vtab.ModuleRegisterer, while a nil db keeps targeting the driver this package registers as sqlite. One existing pattern changes behavior, narrowly and loudly: vtab.RegisterModule(db, ...) where db was opened on a caller-constructed Driver used to discard the db argument and land on the sqlite driver, reaching every connection in the process; it now lands on the constructed driver alone, so a sql.Open("sqlite") connection that used to resolve such a module gets no such module instead. The same pattern is also the one way an existing program could hold one module name on both a constructed Driver and the package-level one: there the first of the two registrations used to win and the second was refused as already registered, whereas now the package-level implementation wins on the constructed Driver's connections regardless of the order they ran in. Reaching that case at all means the program ignored an error the older version returned. Two smaller deviations round out the list: Driver.RegisterModule reports no error for such a collision, and vtab.RegisterModule now validates its name and module arguments before the not-implemented check, so a call with an empty name that returned vtab: RegisterModule not wired into engine outside this driver returns vtab: module name must be non-empty instead. Everything else is additive against v1.56.0: the package-level registration functions target the same driver they always did, connections still receive every module registered through the package-level path whichever Driver opened them, and a db opened on the sqlite driver resolves to that same driver. The isolating change discussed in [GitLab issue #254](https://gitlab.com/cznic/sqlite/-/issues/254) is deliberately not made here.
    • See [GitLab merge request #135](https://gitlab.com/cznic/sqlite/-/merge_requests/135), thanks Ian Chechin!
    • Promote freebsd/386, freebsd/arm and netbsd/amd64 to fully supported platforms. All three are now listed in the package documentation's platform table, which had carried seventeen entries while this module shipped, cross-built and tested twenty. They arrived as experimental in v1.53.0 — netbsd/amd64 reviving a port that had been broken for years, freebsd/386 replacing a stale, effectively untested SQLite 3.41 transpile, and freebsd/arm entirely new — and were deliberately kept out of that table until they had accumulated real-world exposure, with promotion promised once "a period of broader real-world testing … elapses without surprises". That period has elapsed: all three have been in the builder test matrix and in make build_all_targets since v1.53.0, all three pass the full test suite on this release's commit alongside the seventeen platforms already listed, and no open issue reports a defect in any of them. The two netbsd/amd64 build failures filed before the revival, [GitLab issue #202](https://gitlab.com/cznic/sqlite/-/issues/202) and [GitLab issue #234](https://gitlab.com/cznic/sqlite/-/issues/234), no longer reproduce at this commit: Xsqlite3_is_interrupted is present in the sources that target selects, and the mu.enter/mu.leave symbols that broke the build are gone. Documentation only — the transpiled sources under lib/ are byte-for-byte what v1.56.0 shipped, and nothing about how these targets behave changes.

  • 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 re...

      Description has been truncated

@dependabot
chore(deps): bump the go-modules group with 14 updates
8ad18ef 
Bumps the go-modules group with 14 updates:

| Package | From | To |
| --- | --- | --- |
| [github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go) | `1.36.0` | `1.37.0` |
| [github.com/GoogleCloudPlatform/opentelemetry-operations-go/exporter/metric](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go) | `0.60.0` | `0.61.0` |
| [github.com/GoogleCloudPlatform/opentelemetry-operations-go/internal/resourcemapping](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go) | `0.60.0` | `0.61.0` |
| [github.com/aws/aws-sdk-go-v2/config](https://github.com/aws/aws-sdk-go-v2) | `1.33.1` | `1.33.2` |
| [github.com/aws/aws-sdk-go-v2/credentials](https://github.com/aws/aws-sdk-go-v2) | `1.20.1` | `1.20.2` |
| [github.com/aws/aws-sdk-go-v2/service/s3](https://github.com/aws/aws-sdk-go-v2) | `1.109.1` | `1.110.0` |
| [github.com/aws/aws-sdk-go-v2/service/signin](https://github.com/aws/aws-sdk-go-v2) | `1.7.1` | `1.8.0` |
| [github.com/aws/aws-sdk-go-v2/service/sso](https://github.com/aws/aws-sdk-go-v2) | `1.35.1` | `1.36.0` |
| [github.com/aws/aws-sdk-go-v2/service/ssooidc](https://github.com/aws/aws-sdk-go-v2) | `1.40.1` | `1.41.0` |
| [github.com/aws/aws-sdk-go-v2/service/sts](https://github.com/aws/aws-sdk-go-v2) | `1.47.1` | `1.48.0` |
| [github.com/ebitengine/purego](https://github.com/ebitengine/purego) | `0.10.2` | `0.11.0` |
| [github.com/gpustack/gguf-parser-go](https://github.com/gpustack/gguf-parser-go) | `0.26.2` | `0.26.3` |
| [google.golang.org/api](https://github.com/googleapis/google-api-go-client) | `0.295.0` | `0.296.0` |
| [modernc.org/sqlite](https://gitlab.com/cznic/sqlite) | `1.57.0` | `1.58.0` |


Updates `github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp` from 1.36.0 to 1.37.0
- [Release notes](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/releases)
- [Commits](GoogleCloudPlatform/opentelemetry-operations-go@detectors/gcp/v1.36.0...detectors/gcp/v1.37.0)

Updates `github.com/GoogleCloudPlatform/opentelemetry-operations-go/exporter/metric` from 0.60.0 to 0.61.0
- [Release notes](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/releases)
- [Commits](GoogleCloudPlatform/opentelemetry-operations-go@v0.60.0...v0.61.0)

Updates `github.com/GoogleCloudPlatform/opentelemetry-operations-go/internal/resourcemapping` from 0.60.0 to 0.61.0
- [Release notes](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/releases)
- [Commits](GoogleCloudPlatform/opentelemetry-operations-go@v0.60.0...v0.61.0)

Updates `github.com/aws/aws-sdk-go-v2/config` from 1.33.1 to 1.33.2
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@config/v1.33.1...config/v1.33.2)

Updates `github.com/aws/aws-sdk-go-v2/credentials` from 1.20.1 to 1.20.2
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@v1.20.1...v1.20.2)

Updates `github.com/aws/aws-sdk-go-v2/service/s3` from 1.109.1 to 1.110.0
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@service/s3/v1.109.1...service/s3/v1.110.0)

Updates `github.com/aws/aws-sdk-go-v2/service/signin` from 1.7.1 to 1.8.0
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Changelog](https://github.com/aws/aws-sdk-go-v2/blob/v1.8.0/CHANGELOG.md)
- [Commits](aws/aws-sdk-go-v2@v1.7.1...v1.8.0)

Updates `github.com/aws/aws-sdk-go-v2/service/sso` from 1.35.1 to 1.36.0
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@service/pi/v1.35.1...v1.36.0)

Updates `github.com/aws/aws-sdk-go-v2/service/ssooidc` from 1.40.1 to 1.41.0
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@v1.40.1...v1.41.0)

Updates `github.com/aws/aws-sdk-go-v2/service/sts` from 1.47.1 to 1.48.0
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@service/s3/v1.47.1...service/s3/v1.48.0)

Updates `github.com/ebitengine/purego` from 0.10.2 to 0.11.0
- [Release notes](https://github.com/ebitengine/purego/releases)
- [Commits](ebitengine/purego@v0.10.2...v0.11.0)

Updates `github.com/gpustack/gguf-parser-go` from 0.26.2 to 0.26.3
- [Release notes](https://github.com/gpustack/gguf-parser-go/releases)
- [Commits](gpustack/gguf-parser-go@v0.26.2...v0.26.3)

Updates `google.golang.org/api` from 0.295.0 to 0.296.0
- [Release notes](https://github.com/googleapis/google-api-go-client/releases)
- [Changelog](https://github.com/googleapis/google-api-go-client/blob/main/CHANGES.md)
- [Commits](googleapis/google-api-go-client@v0.295.0...v0.296.0)

Updates `modernc.org/sqlite` from 1.57.0 to 1.58.0
- [Changelog](https://gitlab.com/cznic/sqlite/blob/master/CHANGELOG.md)
- [Commits](https://gitlab.com/cznic/sqlite/compare/v1.57.0...v1.58.0)

---
updated-dependencies:
- dependency-name: github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp
  dependency-version: 1.37.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-modules
- dependency-name: github.com/GoogleCloudPlatform/opentelemetry-operations-go/exporter/metric
  dependency-version: 0.61.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-modules
- dependency-name: github.com/GoogleCloudPlatform/opentelemetry-operations-go/internal/resourcemapping
  dependency-version: 0.61.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-modules
- dependency-name: github.com/aws/aws-sdk-go-v2/config
  dependency-version: 1.33.2
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: go-modules
- dependency-name: github.com/aws/aws-sdk-go-v2/credentials
  dependency-version: 1.20.2
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: go-modules
- dependency-name: github.com/aws/aws-sdk-go-v2/service/s3
  dependency-version: 1.110.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-modules
- dependency-name: github.com/aws/aws-sdk-go-v2/service/signin
  dependency-version: 1.8.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-modules
- dependency-name: github.com/aws/aws-sdk-go-v2/service/sso
  dependency-version: 1.36.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-modules
- dependency-name: github.com/aws/aws-sdk-go-v2/service/ssooidc
  dependency-version: 1.41.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-modules
- dependency-name: github.com/aws/aws-sdk-go-v2/service/sts
  dependency-version: 1.48.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-modules
- dependency-name: github.com/ebitengine/purego
  dependency-version: 0.11.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-modules
- dependency-name: github.com/gpustack/gguf-parser-go
  dependency-version: 0.26.3
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: go-modules
- dependency-name: google.golang.org/api
  dependency-version: 0.296.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-modules
- dependency-name: modernc.org/sqlite
  dependency-version: 1.58.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-modules
...

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 Sep 4, 2026
@dependabot
dependabot Bot requested review from a team as code owners September 4, 2026 15:33
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Sep 4, 2026
@paketo-bot paketo-bot added the semver:patch A change requiring a patch version bump label Sep 4, 2026
@paketo-bot
paketo-bot merged commit 90bf779 into main Sep 4, 2026
11 of 12 checks passed
@paketo-bot
paketo-bot deleted the dependabot/go_modules/go-modules-4970b5b3c3 branch September 4, 2026 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@paketo-bot-reviewer paketo-bot-reviewer paketo-bot-reviewer approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code semver:patch A change requiring a patch version bump

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@paketo-bot-reviewer @paketo-bot