opensearch-go v4.8.1

CRITICAL UPGRADE RELEASE NOTE - v5 has substantially expanded error handling capabilities compared to v4.

v5.0.0 is out, and v4 is now in maintenance mode. v4.8.1 is a maintenance release: it does not add features. The v4 -> v5 upgrade changes runtime error-handling behavior and is NOT a drop-in replacement across major versions. If you use this client, read this now - even if you are only upgrading to v4.8.1.

v4 only returns transport-level errors; partial failures (e.g. failed bulk items, failed shards, unconfirmed replica writes) are reported inside the response body, not as Go error values. In v5, those partial failures are returned as errors by default. Code that compiles and passes against v4 can behave differently against v5 without any code change.

Upgrading between v4 releases (any <v4.8.1 to any v4.X.X) does not change the default error-handling semantics. See guides/error_handling.md for how to adopt the v5 behavior on v4 before you upgrade, and the v4 to v5 migration guide for the full API delta.

v4.8.1 is a dependency patch on top of v4.8.0. No client code changed.

Its main purpose is the Go toolchain. The root module and cmd/osgen now declare go 1.26.0 with toolchain go1.26.9, so builds in this repository use a Go release with the standard library CVE fixes from 1.26.9 (13 advisories that affect 1.26.8, 10 of them reachable from this code). The minimum Go version for building against v4 drops from 1.26.8 to 1.26.0. A toolchain line does not apply to modules that depend on this one, so build your own binaries with Go 1.26.9 or newer to get the fixes.

Full Changelog: v4.8.0...v4.8.1

4.8.1 Dependencies

• Set go 1.26.0 with toolchain go1.26.9 in the root module and cmd/osgen. By @ryanyuan in #1192
• Bump the AWS SDK for Go v2 to its latest patch releases, github.com/aws/smithy-go to 1.28.2, github.com/tidwall/pretty to 1.2.2, and github.com/go-openapi/jsonpointer to 1.0.2 in cmd/osgen. By @ryanyuan in #1192

See CHANGELOG.md for the full list.

Contributors

Thanks to everyone who contributed to this release: @ryanyuan and @sean-.