Skip to content

build(deps): bump the go-deps group across 1 directory with 18 updates - #7441

Closed
dependabot[bot] wants to merge 7 commits into
mainfrom
dependabot/go_modules/go-deps-2621e3d13d
Closed

dependabot[bot] wants to merge 7 commits into
mainfrom
dependabot/go_modules/go-deps-2621e3d13d

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the go-deps group with 18 updates in the / directory:

Package From To
github.com/anthropics/anthropic-sdk-go 1.71.0 1.78.0
github.com/dolthub/driver/v2 2.2.0 2.4.1
github.com/gowebpki/jcs 1.0.1 1.0.2
go.opentelemetry.io/otel 1.46.0 1.47.0
go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp 1.46.0 1.47.0
go.opentelemetry.io/otel/exporters/stdout/stdoutmetric 1.46.0 1.47.0
go.opentelemetry.io/otel/exporters/stdout/stdouttrace 1.46.0 1.47.0
go.opentelemetry.io/otel/metric 1.46.0 1.47.0
go.opentelemetry.io/otel/sdk 1.46.0 1.47.0
go.opentelemetry.io/otel/sdk/metric 1.46.0 1.47.0
go.opentelemetry.io/otel/trace 1.46.0 1.47.0
golang.org/x/sync 0.23.0 0.24.0
golang.org/x/sys 0.48.0 0.49.0
github.com/dolthub/dolt/go 0.40.5-0.20260806213044-796d07497741 0.40.5-0.20261002233748-c6af56fead88
github.com/dolthub/go-mysql-server 0.20.1-0.20260805191915-e5eafe0da809 0.20.1-0.20261001232740-19405eb6f203
github.com/dolthub/vitess 0.0.0-20260728212736-0542037326d7 0.0.0-20260930232419-a6b7b0c65d17
golang.org/x/mod 0.40.0 0.41.0
golang.org/x/net 0.58.0 0.59.0

Updates github.com/anthropics/anthropic-sdk-go from 1.71.0 to 1.78.0

Release notes

Sourced from github.com/anthropics/anthropic-sdk-go's releases.

v1.78.0

1.78.0 (2026-09-30)

Full Changelog: v1.77.0...v1.78.0

Features

  • api: add list spend limits endpoint (597ed95)

Chores

  • api: mark Claude Sonnet 4.5 as deprecated (end-of-life November 30, 2026) (5464a3e)

v1.77.0

1.77.0 (2026-09-30)

Full Changelog: v1.76.0...v1.77.0

Features

  • analytics: keep the per-user report actor a union (#416) (03b3feb)
  • api: add a refusal stop reason and stop_details to Managed Agents session idle events (2225664)
  • api: add Claude Enterprise analytics, spend limits, and RBAC groups and roles to the Admin API (9039d31)
  • api: add per-user usage and cost reports to the Admin API analytics (14fa777)
  • api: add Plugins and Plugin Marketplaces to the Admin API (785997a)
  • api: add repository error types to Managed Agents session errors (9dfb79b)
  • api: allow removing a plugin's org-wide installation setting (ef365f2)
  • api: MCP tunnels beta: add read-only transport object to Tunnel and return the one-time relay token in the create response (f6572a5)
  • api: Organization API endpoints are now GA (4fc56d2)

Bug Fixes

  • api: make memory store description, metadata, archived_at required (b8bf04b)
  • api: type admin plugin preference and marketplace fields as enums (9e2de19)
  • client: redact sensitive headers in DumpRequest and DumpResponse (f57d275)
  • pagination: auto-paging continues past an empty page while next_page is set (2c8cdd7)
  • tools: stop the session tool runner after any idle that ends the turn (#413) (bb2421f)

Chores

  • api: update MCP Tunnels types and descriptions (1b0aac7)
  • docs: remove placeholder enum descriptions (d156e86)
  • tests: platform clients do not mirror the Organization service (#414) (108cfae)

v1.76.0

1.76.0 (2026-09-28)

... (truncated)

Changelog

Sourced from github.com/anthropics/anthropic-sdk-go's changelog.

1.78.0 (2026-09-30)

Full Changelog: v1.77.0...v1.78.0

Features

  • api: add list spend limits endpoint (597ed95)

Chores

  • api: mark Claude Sonnet 4.5 as deprecated (end-of-life November 30, 2026) (5464a3e)

1.77.0 (2026-09-30)

Full Changelog: v1.76.0...v1.77.0

Features

  • analytics: keep the per-user report actor a union (#416) (03b3feb)
  • api: add a refusal stop reason and stop_details to Managed Agents session idle events (2225664)
  • api: add Claude Enterprise analytics, spend limits, and RBAC groups and roles to the Admin API (9039d31)
  • api: add per-user usage and cost reports to the Admin API analytics (14fa777)
  • api: add Plugins and Plugin Marketplaces to the Admin API (785997a)
  • api: add repository error types to Managed Agents session errors (9dfb79b)
  • api: allow removing a plugin's org-wide installation setting (ef365f2)
  • api: MCP tunnels beta: add read-only transport object to Tunnel and return the one-time relay token in the create response (f6572a5)
  • api: Organization API endpoints are now GA (4fc56d2)

Bug Fixes

  • api: make memory store description, metadata, archived_at required (b8bf04b)
  • api: type admin plugin preference and marketplace fields as enums (9e2de19)
  • client: redact sensitive headers in DumpRequest and DumpResponse (f57d275)
  • pagination: auto-paging continues past an empty page while next_page is set (2c8cdd7)
  • tools: stop the session tool runner after any idle that ends the turn (#413) (bb2421f)

Chores

  • api: update MCP Tunnels types and descriptions (1b0aac7)
  • docs: remove placeholder enum descriptions (d156e86)
  • tests: platform clients do not mirror the Organization service (#414) (108cfae)

1.76.0 (2026-09-28)

Full Changelog: v1.75.0...v1.76.0

Features

... (truncated)

Commits
  • c9ebe44 Merge pull request #448 from anthropics/release-please--branches--main--chang...
  • 1e8c4aa release: 1.78.0
  • 5464a3e chore(api): mark Claude Sonnet 4.5 as deprecated (end-of-life November 30, 2026)
  • 597ed95 feat(api): add list spend limits endpoint
  • 4fb7c7f Merge branch 'main' into next
  • ccc5e06 Merge pull request #447 from anthropics/release-please--branches--main--chang...
  • 617823d release: 1.77.0
  • 03b3feb feat(analytics): keep the per-user report actor a union (#416)
  • bb2421f fix(tools): stop the session tool runner after any idle that ends the turn (#...
  • 108cfae chore(tests): platform clients do not mirror the Organization service (#414)
  • Additional commits viewable in compare view

Updates github.com/dolthub/driver/v2 from 2.2.0 to 2.4.1

Release notes

Sourced from github.com/dolthub/driver/v2's releases.

v2.4.1

What's Changed

Full Changelog: dolthub/driver@v2.4.0...v2.4.1

v2.4.0

What's Changed

Full Changelog: dolthub/driver@v2.2.0...v2.4.0

Commits
  • 50420f9 Merge pull request #653 from dolthub/bump-dolt-c6af56fe
  • b7fac5b [ga-bump-dep] Bump dolt to c6af56fead88de80c3dc42e0f948689494691274
  • 4c7b897 Merge pull request #643 from dolthub/bump-dolt-863fefb7
  • 81e88c6 [ga-bump-dep] Bump dolt to 863fefb78c630ab4f6f3ec62cb8b060d7cfed398
  • 240fe6c Merge pull request #595 from dolthub/bump-dolt-b97cd470
  • c04ec36 [ga-bump-dep] Bump dolt to b97cd470f16f29051516994e219d9fdd3e7a1a9c
  • 61ccedb Merge pull request #572 from dolthub/bump-dolt-362a8652
  • 9d48424 [ga-bump-dep] Bump dolt to 362a86528a8ab45389eeed59f1b4de5b3a72c981
  • 6590046 Merge pull request #565 from dolthub/bump-dolt-92d7b6a8
  • 95e8fff [ga-bump-dep] Bump dolt to 92d7b6a88ece44ab30a62aafaeaa110d109ca12e
  • Additional commits viewable in compare view

Updates github.com/gowebpki/jcs from 1.0.1 to 1.0.2

Release notes

Sourced from github.com/gowebpki/jcs's releases.

Version 1.0.2

A fully implemented version of RFC 8785 for Golang with fixes for various bugs.

Commits

Updates go.opentelemetry.io/otel from 1.46.0 to 1.47.0

Release notes

Sourced from go.opentelemetry.io/otel's releases.

v1.47.0/v0.69.0/v0.23.0/v0.1.0

This release contains the first stable release of the OpenTelemetry Go Logs API and SDK. Our project stability guarantees now apply to the following modules:

  • go.opentelemetry.io/otel/log
  • go.opentelemetry.io/otel/sdk/log

See our versioning policy for more information about these stability guarantees.

Added

  • Add String method for KeyValue type in go.opentelemetry.io/otel/attribute. (#8205)
  • Add String method for Set type in go.opentelemetry.io/otel/attribute. (#8347)
  • Add WithMaxExportBatchSize to go.opentelemetry.io/otel/sdk/metric to configure the maximum export batch size for PeriodicReader. (#8960)
  • Add WithAttributeValueDepthLimit, DefaultAttributeValueDepthLimit, and SpanLimits.AttributeValueDepthLimit in go.opentelemetry.io/otel/sdk/trace to configure the maximum depth of span, event, link, and instrumentation scope attribute values. (#8938)
  • Add WithAttributeValueDepthLimit in go.opentelemetry.io/otel/sdk/log to configure the maximum depth of log record and instrumentation scope attribute values. (#8938)
  • Add WithMaxResponseSize to go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp, go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp, and go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp. (#8941)
  • Add experimental ProbabilitySampler in go.opentelemetry.io/otel/sdk/trace/x that conforms to the OpenTelemetry specification's threshold-based sampling algorithm. (#8123)
  • Add experimental *Binder extension interfaces in go.opentelemetry.io/otel/metric/x for instruments that support binding attributes ahead of time. (#8760)
  • Add the experimental Finisher synchronous metric instrument extension interface to go.opentelemetry.io/otel/metric/x. (#8906)

Changed

  • Use the OpenTelemetry Attribute Collection representation for non-OTLP protocols for metric data diffs in go.opentelemetry.io/otel/sdk/metric/metricdata/metricdatatest. (#8993)
  • Apply a maximum depth of 64 by default to span, event, link, log record, and instrumentation scope attribute values in go.opentelemetry.io/otel/sdk/trace and go.opentelemetry.io/otel/sdk/log. (#8938)
  • Reduce allocations when applying attribute value length limits in go.opentelemetry.io/otel/sdk/trace and go.opentelemetry.io/otel/sdk/log by rebuilding composite values only when truncation is needed. (#8912)
  • Decode traceparent using a hex lookup table in go.opentelemetry.io/otel/propagation, which rejects the specification-disallowed upper-case characters without a separate scan of the header. (#8739)
  • Decode all characters at constant indices in TraceIDFromHex and SpanIDFromHex in go.opentelemetry.io/otel/trace to eliminate bounds checks. (#8740)

Fixed

  • Count valid U+FFFD replacement characters toward attribute value length limits in go.opentelemetry.io/otel/trace, go.opentelemetry.io/otel/sdk/trace, and go.opentelemetry.io/otel/sdk/log.
  • Truncate string attribute values to empty strings when the configured length limit is zero, including malformed UTF-8, in go.opentelemetry.io/otel/trace, go.opentelemetry.io/otel/sdk/trace, and go.opentelemetry.io/otel/sdk/log. (#9054)
  • Fix a data race in NewPeriodicReader where r.inst was assigned after the background goroutine was launched in go.opentelemetry.io/otel/sdk/metric. (#9028)
  • Prevent precision loss for large int64 values in Sum, Histogram, and ExponentialHistogram aggregations in go.opentelemetry.io/otel/sdk/metric. (#8981)
  • Ensure grpc.DialOption values passed via WithDialOption take precedence over conflicting internally-computed defaults in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc, go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc, and go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc. (#8805, #8834, #8836)
  • Treat overflowing OTEL_METRIC_EXPORT_INTERVAL and OTEL_METRIC_EXPORT_TIMEOUT values as invalid in go.opentelemetry.io/otel/sdk/metric. (#8800)
  • Prevent a panic in NewFixedSizeReservoir and FixedSizeReservoirProvider when given a negative size in go.opentelemetry.io/otel/sdk/metric/exemplar; negative sizes are now clamped to zero, consistent with a size of zero. (#8832)
  • Preserve exponential histogram ZeroThreshold during OTLP metric export in go.opentelemetry.io/otel/exporters/otlp/otlpmetric. (#8801)
  • Ensure metric helpers in go.opentelemetry.io/otel/semconv/v1.32.0, go.opentelemetry.io/otel/semconv/v1.33.0, and go.opentelemetry.io/otel/semconv/v1.34.0 record measurements only once when no attributes are provided. (#8849)
  • Treat empty OTEL_TRACES_SAMPLER and OTEL_TRACES_SAMPLER_ARG values as unset in go.opentelemetry.io/otel/sdk/trace. (#8873)
  • Normalize global OTEL_EXPORTER_OTLP_ENDPOINT path joining in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp so trailing-slash base URLs do not produce double-slash log export paths. (#8864)
  • Prevent a deadlock when formatting an error passed to RecordError calls back into the span in go.opentelemetry.io/otel/sdk/trace. (#8815)
  • Prevent SimpleSpanProcessor.Shutdown from panicking when constructed with a nil exporter in go.opentelemetry.io/otel/sdk/trace. (#8844)
  • Propagate invalid exponential histogram scale errors to Prometheus exporter self-observability metrics in go.opentelemetry.io/otel/exporters/prometheus. (#8839)

... (truncated)

Changelog

Sourced from go.opentelemetry.io/otel's changelog.

[1.47.0/0.69.0/0.23.0/0.1.0] - 2026-10-02

This release contains the first stable release of the OpenTelemetry Go Logs API and SDK. Our project stability guarantees now apply to the following modules:

  • go.opentelemetry.io/otel/log
  • go.opentelemetry.io/otel/sdk/log

See our versioning policy for more information about these stability guarantees.

Added

  • Add String method for KeyValue type in go.opentelemetry.io/otel/attribute. (#8205)
  • Add String method for Set type in go.opentelemetry.io/otel/attribute. (#8347)
  • Add WithMaxExportBatchSize to go.opentelemetry.io/otel/sdk/metric to configure the maximum export batch size for PeriodicReader. (#8960)
  • Add WithAttributeValueDepthLimit, DefaultAttributeValueDepthLimit, and SpanLimits.AttributeValueDepthLimit in go.opentelemetry.io/otel/sdk/trace to configure the maximum depth of span, event, link, and instrumentation scope attribute values. (#8938)
  • Add WithAttributeValueDepthLimit in go.opentelemetry.io/otel/sdk/log to configure the maximum depth of log record and instrumentation scope attribute values. (#8938)
  • Add WithMaxResponseSize to go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp, go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp, and go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp. (#8941)
  • Add experimental ProbabilitySampler in go.opentelemetry.io/otel/sdk/trace/x that conforms to the OpenTelemetry specification's threshold-based sampling algorithm. (#8123)
  • Add experimental *Binder extension interfaces in go.opentelemetry.io/otel/metric/x for instruments that support binding attributes ahead of time. (#8760)
  • Add the experimental Finisher synchronous metric instrument extension interface to go.opentelemetry.io/otel/metric/x. (#8906)

Changed

  • Use the OpenTelemetry Attribute Collection representation for non-OTLP protocols for metric data diffs in go.opentelemetry.io/otel/sdk/metric/metricdata/metricdatatest. (#8993)
  • Apply a maximum depth of 64 by default to span, event, link, log record, and instrumentation scope attribute values in go.opentelemetry.io/otel/sdk/trace and go.opentelemetry.io/otel/sdk/log. (#8938)
  • Reduce allocations when applying attribute value length limits in go.opentelemetry.io/otel/sdk/trace and go.opentelemetry.io/otel/sdk/log by rebuilding composite values only when truncation is needed. (#8912)
  • Decode traceparent using a hex lookup table in go.opentelemetry.io/otel/propagation, which rejects the specification-disallowed upper-case characters without a separate scan of the header. (#8739)
  • Decode all characters at constant indices in TraceIDFromHex and SpanIDFromHex in go.opentelemetry.io/otel/trace to eliminate bounds checks. (#8740)

Fixed

  • Count valid U+FFFD replacement characters toward attribute value length limits in go.opentelemetry.io/otel/trace, go.opentelemetry.io/otel/sdk/trace, and go.opentelemetry.io/otel/sdk/log.
  • Truncate string attribute values to empty strings when the configured length limit is zero, including malformed UTF-8, in go.opentelemetry.io/otel/trace, go.opentelemetry.io/otel/sdk/trace, and go.opentelemetry.io/otel/sdk/log. (#9054)
  • Fix a data race in NewPeriodicReader where r.inst was assigned after the background goroutine was launched in go.opentelemetry.io/otel/sdk/metric. (#9028)
  • Prevent precision loss for large int64 values in Sum, Histogram, and ExponentialHistogram aggregations in go.opentelemetry.io/otel/sdk/metric. (#8981)
  • Ensure grpc.DialOption values passed via WithDialOption take precedence over conflicting internally-computed defaults in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc, go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc, and go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc. (#8805, #8834, #8836)
  • Treat overflowing OTEL_METRIC_EXPORT_INTERVAL and OTEL_METRIC_EXPORT_TIMEOUT values as invalid in go.opentelemetry.io/otel/sdk/metric. (#8800)
  • Prevent a panic in NewFixedSizeReservoir and FixedSizeReservoirProvider when given a negative size in go.opentelemetry.io/otel/sdk/metric/exemplar; negative sizes are now clamped to zero, consistent with a size of zero. (#8832)
  • Preserve exponential histogram ZeroThreshold during OTLP metric export in go.opentelemetry.io/otel/exporters/otlp/otlpmetric. (#8801)
  • Ensure metric helpers in go.opentelemetry.io/otel/semconv/v1.32.0, go.opentelemetry.io/otel/semconv/v1.33.0, and go.opentelemetry.io/otel/semconv/v1.34.0 record measurements only once when no attributes are provided. (#8849)
  • Treat empty OTEL_TRACES_SAMPLER and OTEL_TRACES_SAMPLER_ARG values as unset in go.opentelemetry.io/otel/sdk/trace. (#8873)
  • Normalize global OTEL_EXPORTER_OTLP_ENDPOINT path joining in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp so trailing-slash base URLs do not produce double-slash log export paths. (#8864)
  • Prevent a deadlock when formatting an error passed to RecordError calls back into the span in go.opentelemetry.io/otel/sdk/trace. (#8815)
  • Prevent SimpleSpanProcessor.Shutdown from panicking when constructed with a nil exporter in go.opentelemetry.io/otel/sdk/trace. (#8844)

... (truncated)

Commits
  • 66cfc95 Release 1.47.0/0.69.0/0.23.0/0.1.0 (#9024)
  • f09d1de Merge commit from fork
  • 017b08c Merge commit from fork
  • d9d3ac2 Update ubuntu:26.04 Docker digest to 88a381d
  • b240391 Update module github.com/uudashr/iface to v1.5.3
  • 55899e3 Fix zero attribute value length for malformed UTF-8 (#9054)
  • 75b1fe3 Update github.com/charmbracelet/ultraviolet digest to 8786532
  • cce78ad Update github.com/golangci/rowserrcheck digest to f772fe6 (#9066)
  • cdc6ee4 Update module github.com/pjbgf/sha1cd to v0.7.0
  • ef11bfc chore: Replace deprecated gofumpt extra-rules with extra options (#9062)
  • Additional commits viewable in compare view

Updates go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp from 1.46.0 to 1.47.0

Release notes

Sourced from go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp's releases.

v1.47.0/v0.69.0/v0.23.0/v0.1.0

This release contains the first stable release of the OpenTelemetry Go Logs API and SDK. Our project stability guarantees now apply to the following modules:

  • go.opentelemetry.io/otel/log
  • go.opentelemetry.io/otel/sdk/log

See our versioning policy for more information about these stability guarantees.

Added

  • Add String method for KeyValue type in go.opentelemetry.io/otel/attribute. (#8205)
  • Add String method for Set type in go.opentelemetry.io/otel/attribute. (#8347)
  • Add WithMaxExportBatchSize to go.opentelemetry.io/otel/sdk/metric to configure the maximum export batch size for PeriodicReader. (#8960)
  • Add WithAttributeValueDepthLimit, DefaultAttributeValueDepthLimit, and SpanLimits.AttributeValueDepthLimit in go.opentelemetry.io/otel/sdk/trace to configure the maximum depth of span, event, link, and instrumentation scope attribute values. (#8938)
  • Add WithAttributeValueDepthLimit in go.opentelemetry.io/otel/sdk/log to configure the maximum depth of log record and instrumentation scope attribute values. (#8938)
  • Add WithMaxResponseSize to go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp, go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp, and go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp. (#8941)
  • Add experimental ProbabilitySampler in go.opentelemetry.io/otel/sdk/trace/x that conforms to the OpenTelemetry specification's threshold-based sampling algorithm. (#8123)
  • Add experimental *Binder extension interfaces in go.opentelemetry.io/otel/metric/x for instruments that support binding attributes ahead of time. (#8760)
  • Add the experimental Finisher synchronous metric instrument extension interface to go.opentelemetry.io/otel/metric/x. (#8906)

Changed

  • Use the OpenTelemetry Attribute Collection representation for non-OTLP protocols for metric data diffs in go.opentelemetry.io/otel/sdk/metric/metricdata/metricdatatest. (#8993)
  • Apply a maximum depth of 64 by default to span, event, link, log record, and instrumentation scope attribute values in go.opentelemetry.io/otel/sdk/trace and go.opentelemetry.io/otel/sdk/log. (#8938)
  • Reduce allocations when applying attribute value length limits in go.opentelemetry.io/otel/sdk/trace and go.opentelemetry.io/otel/sdk/log by rebuilding composite values only when truncation is needed. (#8912)
  • Decode traceparent using a hex lookup table in go.opentelemetry.io/otel/propagation, which rejects the specification-disallowed upper-case characters without a separate scan of the header. (#8739)
  • Decode all characters at constant indices in TraceIDFromHex and SpanIDFromHex in go.opentelemetry.io/otel/trace to eliminate bounds checks. (#8740)

Fixed

  • Count valid U+FFFD replacement characters toward attribute value length limits in go.opentelemetry.io/otel/trace, go.opentelemetry.io/otel/sdk/trace, and go.opentelemetry.io/otel/sdk/log.
  • Truncate string attribute values to empty strings when the configured length limit is zero, including malformed UTF-8, in go.opentelemetry.io/otel/trace, go.opentelemetry.io/otel/sdk/trace, and go.opentelemetry.io/otel/sdk/log. (#9054)
  • Fix a data race in NewPeriodicReader where r.inst was assigned after the background goroutine was launched in go.opentelemetry.io/otel/sdk/metric. (#9028)
  • Prevent precision loss for large int64 values in Sum, Histogram, and ExponentialHistogram aggregations in go.opentelemetry.io/otel/sdk/metric. (#8981)
  • Ensure grpc.DialOption values passed via WithDialOption take precedence over conflicting internally-computed defaults in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc, go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc, and go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc. (#8805, #8834, #8836)
  • Treat overflowing OTEL_METRIC_EXPORT_INTERVAL and OTEL_METRIC_EXPORT_TIMEOUT values as invalid in go.opentelemetry.io/otel/sdk/metric. (#8800)
  • Prevent a panic in NewFixedSizeReservoir and FixedSizeReservoirProvider when given a negative size in go.opentelemetry.io/otel/sdk/metric/exemplar; negative sizes are now clamped to zero, consistent with a size of zero. (#8832)
  • Preserve exponential histogram ZeroThreshold during OTLP metric export in go.opentelemetry.io/otel/exporters/otlp/otlpmetric. (#8801)
  • Ensure metric helpers in go.opentelemetry.io/otel/semconv/v1.32.0, go.opentelemetry.io/otel/semconv/v1.33.0, and go.opentelemetry.io/otel/semconv/v1.34.0 record measurements only once when no attributes are provided. (#8849)
  • Treat empty OTEL_TRACES_SAMPLER and OTEL_TRACES_SAMPLER_ARG values as unset in go.opentelemetry.io/otel/sdk/trace. (#8873)
  • Normalize global OTEL_EXPORTER_OTLP_ENDPOINT path joining in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp so trailing-slash base URLs do not produce double-slash log export paths. (#8864)
  • Prevent a deadlock when formatting an error passed to RecordError calls back into the span in go.opentelemetry.io/otel/sdk/trace. (#8815)
  • Prevent SimpleSpanProcessor.Shutdown from panicking when constructed with a nil exporter in go.opentelemetry.io/otel/sdk/trace. (#8844)
  • Propagate invalid exponential histogram scale errors to Prometheus exporter self-observability metrics in go.opentelemetry.io/otel/exporters/prometheus. (#8839)

... (truncated)

Changelog

Sourced from go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp's changelog.

[1.47.0/0.69.0/0.23.0/0.1.0] - 2026-10-02

This release contains the first stable release of the OpenTelemetry Go Logs API and SDK. Our project stability guarantees now apply to the following modules:

  • go.opentelemetry.io/otel/log
  • go.opentelemetry.io/otel/sdk/log

See our versioning policy for more information about these stability guarantees.

Added

  • Add String method for KeyValue type in go.opentelemetry.io/otel/attribute. (#8205)
  • Add String method for Set type in go.opentelemetry.io/otel/attribute. (#8347)
  • Add WithMaxExportBatchSize to go.opentelemetry.io/otel/sdk/metric to configure the maximum export batch size for PeriodicReader. (#8960)
  • Add WithAttributeValueDepthLimit, DefaultAttributeValueDepthLimit, and SpanLimits.AttributeValueDepthLimit in go.opentelemetry.io/otel/sdk/trace to configure the maximum depth of span, event, link, and instrumentation scope attribute values. (#8938)
  • Add WithAttributeValueDepthLimit in go.opentelemetry.io/otel/sdk/log to configure the maximum depth of log record and instrumentation scope attribute values. (#8938)
  • Add WithMaxResponseSize to go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp, go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp, and go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp. (#8941)
  • Add experimental ProbabilitySampler in go.opentelemetry.io/otel/sdk/trace/x that conforms to the OpenTelemetry specification's threshold-based sampling algorithm. (#8123)
  • Add experimental *Binder extension interfaces in go.opentelemetry.io/otel/metric/x for instruments that support binding attributes ahead of time. (#8760)
  • Add the experimental Finisher synchronous metric instrument extension interface to go.opentelemetry.io/otel/metric/x. (#8906)

Changed

  • Use the OpenTelemetry Attribute Collection representation for non-OTLP protocols for metric data diffs in go.opentelemetry.io/otel/sdk/metric/metricdata/metricdatatest. (#8993)
  • Apply a maximum depth of 64 by default to span, event, link, log record, and instrumentation scope attribute values in go.opentelemetry.io/otel/sdk/trace and go.opentelemetry.io/otel/sdk/log. (#8938)
  • Reduce allocations when applying attribute value length limits in go.opentelemetry.io/otel/sdk/trace and go.opentelemetry.io/otel/sdk/log by rebuilding composite values only when truncation is needed. (#8912)
  • Decode traceparent using a hex lookup table in go.opentelemetry.io/otel/propagation, which rejects the specification-disallowed upper-case characters without a separate scan of the header. (#8739)
  • Decode all characters at constant indices in TraceIDFromHex and SpanIDFromHex in go.opentelemetry.io/otel/trace to eliminate bounds checks. (#8740)

Fixed

  • Count valid U+FFFD replacement characters toward attribute value length limits in go.opentelemetry.io/otel/trace, go.opentelemetry.io/otel/sdk/trace, and go.opentelemetry.io/otel/sdk/log.
  • Truncate string attribute values to empty strings when the configured length limit is zero, including malformed UTF-8, in go.opentelemetry.io/otel/trace, go.opentelemetry.io/otel/sdk/trace, and go.opentelemetry.io/otel/sdk/log. (#9054)
  • Fix a data race in NewPeriodicReader where r.inst was assigned after the background goroutine was launched in go.opentelemetry.io/otel/sdk/metric. (#9028)
  • Prevent precision loss for large int64 values in Sum, Histogram, and ExponentialHistogram aggregations in go.opentelemetry.io/otel/sdk/metric. (#8981)
  • Ensure grpc.DialOption values passed via WithDialOption take precedence over conflicting internally-computed defaults in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc, go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc, and go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc. (#8805, #8834, #8836)
  • Treat overflowing OTEL_METRIC_EXPORT_INTERVAL and OTEL_METRIC_EXPORT_TIMEOUT values as invalid in go.opentelemetry.io/otel/sdk/metric. (#8800)
  • Prevent a panic in NewFixedSizeReservoir and FixedSizeReservoirProvider when given a negative size in go.opentelemetry.io/otel/sdk/metric/exemplar; negative sizes are now clamped to zero, consistent with a size of zero. (#8832)
  • Preserve exponential histogram ZeroThreshold during OTLP metric export in go.opentelemetry.io/otel/exporters/otlp/otlpmetric. (#8801)
  • Ensure metric helpers in go.opentelemetry.io/otel/semconv/v1.32.0, go.opentelemetry.io/otel/semconv/v1.33.0, and go.opentelemetry.io/otel/semconv/v1.34.0 record measurements only once when no attributes are provided. (#8849)
  • Treat empty OTEL_TRACES_SAMPLER and OTEL_TRACES_SAMPLER_ARG values as unset in go.opentelemetry.io/otel/sdk/trace. (#8873)
  • Normalize global OTEL_EXPORTER_OTLP_ENDPOINT path joining in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp so trailing-slash base URLs do not produce double-slash log export paths. (#8864)
  • Prevent a deadlock when formatting an error passed to RecordError calls back into the span in go.opentelemetry.io/otel/sdk/trace. (#8815)
  • Prevent SimpleSpanProcessor.Shutdown from panicking when constructed with a nil exporter in go.opentelemetry.io/otel/sdk/trace. (#8844)

... (truncated)

Commits
  • 66cfc95 Release 1.47.0/0.69.0/0.23.0/0.1.0 (#9024)
  • f09d1de Merge commit from fork
  • 017b08c Merge commit from fork
  • d9d3ac2 Update ubuntu:26.04 Docker digest to 88a381d
  • b240391 Update module github.com/uudashr/iface to v1.5.3
  • 55899e3 Fix zero attribute value length for malformed UTF-8 (#9054)
  • 75b1fe3 Update github.com/charmbracelet/ultraviolet digest to 8786532
  • cce78ad Update github.com/golangci/rowserrcheck digest to f772fe6 (#9066)
  • cdc6ee4 Update module github.com/pjbgf/sha1cd to v0.7.0
  • ef11bfc chore: Replace deprecated gofumpt extra-rules with extra options (#9062)
  • Additional commits viewable in compare view

Updates go.opentelemetry.io/otel/exporters/stdout/stdoutmetric from 1.46.0 to 1.47...

Description has been truncated

Bumps the go-deps group with 18 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [github.com/anthropics/anthropic-sdk-go](https://github.com/anthropics/anthropic-sdk-go) | `1.71.0` | `1.78.0` |
| [github.com/dolthub/driver/v2](https://github.com/dolthub/driver) | `2.2.0` | `2.4.1` |
| [github.com/gowebpki/jcs](https://github.com/gowebpki/jcs) | `1.0.1` | `1.0.2` |
| [go.opentelemetry.io/otel](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/exporters/stdout/stdoutmetric](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/exporters/stdout/stdouttrace](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/metric](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/sdk](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/sdk/metric](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/trace](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [golang.org/x/sync](https://github.com/golang/sync) | `0.23.0` | `0.24.0` |
| [golang.org/x/sys](https://github.com/golang/sys) | `0.48.0` | `0.49.0` |
| [github.com/dolthub/dolt/go](https://github.com/dolthub/dolt) | `0.40.5-0.20260806213044-796d07497741` | `0.40.5-0.20261002233748-c6af56fead88` |
| [github.com/dolthub/go-mysql-server](https://github.com/dolthub/go-mysql-server) | `0.20.1-0.20260805191915-e5eafe0da809` | `0.20.1-0.20261001232740-19405eb6f203` |
| [github.com/dolthub/vitess](https://github.com/dolthub/vitess) | `0.0.0-20260728212736-0542037326d7` | `0.0.0-20260930232419-a6b7b0c65d17` |
| [golang.org/x/mod](https://github.com/golang/mod) | `0.40.0` | `0.41.0` |
| [golang.org/x/net](https://github.com/golang/net) | `0.58.0` | `0.59.0` |



Updates `github.com/anthropics/anthropic-sdk-go` from 1.71.0 to 1.78.0
- [Release notes](https://github.com/anthropics/anthropic-sdk-go/releases)
- [Changelog](https://github.com/anthropics/anthropic-sdk-go/blob/main/CHANGELOG.md)
- [Commits](anthropics/anthropic-sdk-go@v1.71.0...v1.78.0)

Updates `github.com/dolthub/driver/v2` from 2.2.0 to 2.4.1
- [Release notes](https://github.com/dolthub/driver/releases)
- [Commits](dolthub/driver@v2.2.0...v2.4.1)

Updates `github.com/gowebpki/jcs` from 1.0.1 to 1.0.2
- [Release notes](https://github.com/gowebpki/jcs/releases)
- [Commits](gowebpki/jcs@v1.0.1...v1.0.2)

Updates `go.opentelemetry.io/otel` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/exporters/stdout/stdoutmetric` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/exporters/stdout/stdouttrace` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/metric` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/sdk` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/sdk/metric` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/trace` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `golang.org/x/sync` from 0.23.0 to 0.24.0
- [Commits](golang/sync@v0.23.0...v0.24.0)

Updates `golang.org/x/sys` from 0.48.0 to 0.49.0
- [Commits](golang/sys@v0.48.0...v0.49.0)

Updates `github.com/dolthub/dolt/go` from 0.40.5-0.20260806213044-796d07497741 to 0.40.5-0.20261002233748-c6af56fead88
- [Release notes](https://github.com/dolthub/dolt/releases)
- [Commits](https://github.com/dolthub/dolt/commits)

Updates `github.com/dolthub/go-mysql-server` from 0.20.1-0.20260805191915-e5eafe0da809 to 0.20.1-0.20261001232740-19405eb6f203
- [Release notes](https://github.com/dolthub/go-mysql-server/releases)
- [Commits](https://github.com/dolthub/go-mysql-server/commits)

Updates `github.com/dolthub/vitess` from 0.0.0-20260728212736-0542037326d7 to 0.0.0-20260930232419-a6b7b0c65d17
- [Commits](https://github.com/dolthub/vitess/commits)

Updates `golang.org/x/mod` from 0.40.0 to 0.41.0
- [Commits](golang/mod@v0.40.0...v0.41.0)

Updates `golang.org/x/net` from 0.58.0 to 0.59.0
- [Commits](golang/net@v0.58.0...v0.59.0)

---
updated-dependencies:
- dependency-name: github.com/anthropics/anthropic-sdk-go
  dependency-version: 1.78.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/dolthub/driver/v2
  dependency-version: 2.4.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/gowebpki/jcs
  dependency-version: 1.0.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/exporters/stdout/stdoutmetric
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/exporters/stdout/stdouttrace
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/metric
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/sdk
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/sdk/metric
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/trace
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: golang.org/x/sync
  dependency-version: 0.24.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: golang.org/x/sys
  dependency-version: 0.49.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/dolthub/dolt/go
  dependency-version: 0.40.5-0.20261002233748-c6af56fead88
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: github.com/dolthub/go-mysql-server
  dependency-version: 0.20.1-0.20261001232740-19405eb6f203
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: github.com/dolthub/vitess
  dependency-version: 0.0.0-20260930232419-a6b7b0c65d17
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: golang.org/x/mod
  dependency-version: 0.41.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: golang.org/x/net
  dependency-version: 0.59.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Dependency updates go Go code and modules labels Oct 9, 2026
@github-actions github-actions Bot added status/needs-triage Awaiting initial PM triage and removed status/needs-triage Awaiting initial PM triage labels Oct 9, 2026

@bee-ghosttrack bee-ghosttrack left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

REQUEST CHANGES (for the maintainer; dependabot cannot act on any of this). Reviewed at head 14ccac9.

This group carries the Dolt family bump — dolthub/driver/v2 2.2.0 → 2.4.1, and with it dolthub/dolt/go → c6af56fead88, go-mysql-server → 19405eb6f203, vitess → a6b7b0c65d17 — which are byte-for-byte the pins of #7254, where the review is still changes-requested on an engine regression. The four red jobs here are four different consequences of that one bump, none of which a dependabot PR can carry the fix for:

1. Bazel / embedded Dolt tier — the #7254 engine regression. 24 occurrences of versioned history: compute next revision for <id>: sql: no rows in result set across embeddeddolt_embedded_test, bd_embedded_part2_test, httpclient_served_test and embeddeddolt_batch_apply_nonrace_test (job 114031086487). Dolt 2.4.0/2.4.1 return zero rows for an ungrouped MAX over an unmatched PK-prefix lookup, where 2.2.0–2.3.5 return one; bracketed with bare release CLIs on #7254 and reported upstream from there. The served-test 404s in the same job (served_dualwrite_history_test.go:129/132) are downstream of the creates that failed on it.

2. Bazel / dolt-server lane — the CLI pin lags the engine. protocol_dolt_test fails 4 of 8 shards: versioning_contract_test.go:43/82/106/134, every one dolt sql -q "INSERT INTO schema_migrations …" / DELETE FROM schema_migrations … → table has unknown fields. That is the 2.2.0 CLI (tools/bazel/dolt.bzl DOLT_VERSION = "2.2.0", scripts/ci/install-dolt.sh version="2.2.0") opening a database the 2.4.1 engine just created. The same shape was named on #6811 and #7254; #7254 moves the pin and adds the 2.4.1 digests. A go.mod-only bump cannot.

3. Bazel / integration — tools/nogo/go.mod is a second module dependabot does not see. TestModuleRequirementsAgreeWithRoot (tools/nogo/modules_test.go:43): golang.org/x/mod v0.40.0 vs root v0.41.0, x/sync v0.23.0 vs v0.24.0, x/text v0.41.0 vs v0.42.0. .github/dependabot.yml's gomod block has directory: "/" only, so this fails on every go-deps group that touches a module the nogo module also requires, independent of Dolt. A durable fix is directories: ["/", "/tools/nogo"] on that block so one grouped PR moves both (the examples/*/go.mod are not under this test).

4. Test Nix Flake → PR Risk Gate — not the vendorHash. Update default.nix vendorHash ran and reported vendorHash already matched; nothing to commit. The build dies earlier: go: github.com/dolthub/driver/v2@v2.4.1: module github.com/dolthub/driver/v2@v2.4.1 requires go >= 1.26.5 (running go 1.26.4; GOTOOLCHAIN=local). default.nix rewrites the ROOT go.mod's go line down to the Nix toolchain's version (postPatch: go mod edit -go="$goVer", with GOTOOLCHAIN=local), but a dependency's own floor cannot be rewritten, and driver v2.4.1's go.mod says go 1.26.5. The flake's go_1_26 is nixpkgs nixos-25.11, which is still 1.26.4 at the branch head today (the lock, b6018f87da91, is the same); nixos-unstable/master carry 1.26.8. So any driver ≥ 2.4.1 needs a nixpkgs input move or a Go override in the flake first. #7254's Test Nix Flake is red with the identical line, so this blocks that PR too and is worth a line there.

Bazel / server-Dolt storage tier passed and Bazel / test was still pending when I posted; neither changes the above.

What would land the other 15 bumps. The Dolt driver bump rides the group only because 2.2.0 → 2.4.1 is a SemVer minor. Until the engine bracket clears (and #7254 or its successor moves the CLI pin, nogo module and Nix floor together), keep the family out of the group with an ignore: entry on the gomod block, e.g. dependency-name: "github.com/dolthub/*", then @dependabot recreate — the remaining bumps (anthropic-sdk-go 1.71 → 1.78, otel 1.46 → 1.47 ×8, jcs, x/sync, x/sys and their indirects) are routine and I would expect the tiers green with item 3 fixed. I have not reviewed those 15 individually at this head; say the word and I will once the PR is recreated without the Dolt lines.

julianknutsen and others added 4 commits October 11, 2026 04:19
dolthub/driver v2.4.1 declares go 1.26.5, but nixos-25.11 is frozen
(last commit 2026-06-30) at go 1.26.4. default.nix's postPatch can only
lower the root module's go directive, not a dependency's, so the Nix
build failed with "requires go >= 1.26.5 (running go 1.26.4;
GOTOOLCHAIN=local)". nixos-26.05 ships go 1.26.8 and keeps
buildGo126Module and go_1_26, and the weekly flake-lock update can
track it.

Recompute vendorHash for the bumped go.sum.

Verified with nixos/nix: nix flake check passes, nix run .#default --
--help works, and the devShell reports go1.26.8.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
TestModuleRequirementsAgreeWithRoot (//tools/nogo:nogo_test) requires
the analyzer module's shared requirements to match go.mod. The go-deps
bump moved the root to x/mod v0.41.0, x/sync v0.24.0 and x/text v0.42.0.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
go-mysql-server's aggregate-over-index rewrite
(dolthub/go-mysql-server#3907, pulled in by the driver v2.4.1 bump)
returns zero rows, not one NULL row, for an ungrouped MAX/MIN over an
empty primary-key prefix:

  SELECT COALESCE(MAX(revision), 0) + 1 FROM issue_versions WHERE issue_id = ?

so every first mint on an issue failed with "versioned history: compute
next revision for X: sql: no rows in result set", breaking the
versioned-history contract tests on the embedded, served, server and UoW
tiers. Wrap the aggregate in a scalar subquery: the outer SELECT has no
FROM and yields exactly one row on every engine, including dolt 2.2.0.

This is the only production query with the affected shape; other
MAX/MIN uses are grouped, unfiltered, range-filtered, or on a secondary
index. Versioned history is only enabled in tests today, so no release
is affected.

Add TestEmbeddedFirstMintOnEmptyHistoryIsRevisionOne, which fails on the
old query and pins that the first mint is revision 1 and the second 2.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Carry #7254's pin bump onto the driver v2.4.1 upgrade. The pinned
dolt 2.2.0 CLI cannot write storage the 2.4.1 engine created: after a
`bd init` through driver v2.4.1, `dolt sql -q "INSERT ..."` fails with
"table has unknown fields" on dolt 2.2.0 and 2.3.1 and succeeds on
2.4.1. That broke the protocol, proxied and TestEmbeddedInit* lanes
wherever a test shells out to `dolt sql`.

The pin policy in install-dolt.sh / dolt.md requires the DOLT_RESET
('--hard') measurement before raising the pin. Measured 2026-10-10:
2.3.1 8/150 broken (positive control), 2.4.1 0/250 over two runs, the
embedded engine via driver v2.4.1 0/60. The docs keep the 2.3.x rows and
the "raise only once measured" rule and add the 2.4.1 row.

- install-dolt.sh, pull-dolt-image.sh, testdoltcommon.go, dolt.bzl
  (DOLT_VERSION plus release digests; linux-amd64 re-hashed locally) and
  the script test constants move to 2.4.1.
- doltversion.RecommendedMin is 2.4.1, documented with the unknown-fields
  evidence; it stays a recommendation, not a hard floor.
- Three fixes #7254 lacked: the doltversion cache tests derive their
  "recent version" stub from RecommendedMin instead of 2.1.0 (now below
  the minimum, which failed the Windows lane); the server fingerprint
  golden takes dolt 2.4.x's default sql_mode; and doltSQLServerImage in
  scripts/repo_helpers_test.go, where main moved it from
  pull_dolt_image_test.go.
- Refresh comments that called 2.2.0 the current CLI pin.

Release note: managed proxied-server mode now recommends dolt >= 2.4.1,
and server-mode users on dolt 2.4.x get the stricter default sql_mode
(adds NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO).

Co-authored-by: coffeegoddd <dustin@dolthub.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@gascityinc-randy

Copy link
Copy Markdown
Contributor

Pushed four commits on top of the Dependabot bump to fix the red checks (fast-forward, no rebase; please do not @dependabot rebase/recreate, it would drop them):

  • f7f41a3df2 build(nix): flake to nixos-26.05. driver v2.4.1 requires go >= 1.26.5; frozen nixos-25.11 ships 1.26.4. vendorHash recomputed (sha256-9A9lzocuEii/t2AHC1ca5uQsB965NqhQW3wpmwklZeg=). Note: update-vendor-hash.yml reported a false "already correct" here, since the script treats any non-hash build failure as success.
  • 65290cca28 build(nogo): align tools/nogo/go.mod x/mod, x/sync, x/text with the root (TestModuleRequirementsAgreeWithRoot).
  • f5a1ed66a6 fix(storage): RecordVersionInTx next revision via a scalar subquery. go-mysql-server's aggregate-over-index rewrite (Optimize aggregate functions and remove sort nodes on multi-column indexes provided that any columns before the aggregated/sorted column are constant  dolthub/go-mysql-server#3907) returns zero rows for an ungrouped MAX(revision) over an empty PK prefix, which broke every first versioned-history mint. Adds TestEmbeddedFirstMintOnEmptyHistoryIsRevisionOne.
  • a8622b53c2 build(dolt): CLI/container/Bazel pins to 2.4.1, carried from build(deps): align Dolt driver and test versions to 2.4.1 #7254 (co-authored by @coffeegoddd), plus the doltversion cache tests, the server-fingerprint sql_mode golden and scripts/repo_helpers_test.go's image constant. The DOLT_RESET('--hard') measurement the pin policy requires: 2.3.1 8/150 broken (control), 2.4.1 0/250, embedded 0/60.

Release notes: doltversion.RecommendedMin is now 2.4.1, because dolt 2.2.0/2.3.1 cannot write storage the 2.4.1 engine created (table has unknown fields). Server-mode users on dolt 2.4.x also get a stricter default sql_mode (adds NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO).

Still expected red: release cross-compile (freebsd/amd64). The new transitive github.com/dolthub/file-locks v0.1.1 only builds on linux/darwin/windows, so this needs an upstream build-tag fix and tag. The Thrift/gRPC security bumps are landing separately in #7495.

Local verification: nix flake check passes; bazel test //tools/nogo:nogo_test //scripts/... //internal/doltversion/... passes; bazel test --config=doltserver //cmd/bd/protocol:protocol_dolt_test passes; bazel test //... --config={embedded,doltserver,doltserver-proxied} all pass; TestDoltServerFingerprint/local passes with the dolt 2.4.1 CLI; cross-compile passes for every target except freebsd.

Resolve the conflict in .github/scripts/embedded-storage-test-shards.txt:
main moved the embedded storage tier to a 40-shard block, so take
main's manifest and place TestEmbeddedFirstMintOnEmptyHistoryIsRevisionOne
with gen_embedded_storage_shard_manifest.py 40 --weights=duration --write.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

@bee-ghosttrack bee-ghosttrack left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

REQUEST CHANGES, re-reviewed at head 27f754d (randy's four fixups + the merge of main). The four items of my 2026-10-09 review are cleared; one new blocker, in a module neither dependabot nor the fixups touched directly.

Cleared. Bazel / embedded Dolt tier, dolt-server lane, integration, test, server-Dolt storage tier, dolt-race and the Windows lanes are green at this head; the Nix flake on nixos-26.05 builds (Test Nix Flake no longer in the rollup as red). Checked beside the diffs:

  • f5a1ed66 — the scalar-subquery form is the right shape for dolthub/go-mysql-server#3907; TestEmbeddedFirstMintOnEmptyHistoryIsRevisionOne is in embedded-storage-test-shards.txt. I grepped the non-test tree for other ungrouped MAX/MIN over a PK-prefix WHERE: derivedid.go:217 (SELECT MAX(created_at) FROM <t> WHERE issue_id = ?) has the same syntactic shape; it is on the created_at/issue_id lookup of the derived-ID tables, and whether #3907's rewrite fires there depends on that table's index — worth a one-line note from the author, not a blocker (the tiers that exercise it are green).
  • a8622b53 — tools/bazel/dolt.bzl 2.4.1 digests equal the GitHub release asset digests for all four platforms (gh api repos/dolthub/dolt/releases/tags/v2.4.1 … .assets[].digest); install-dolt.sh, pull-dolt-image.sh, testdoltcommon.go, the fingerprint golden and install_dolt_test.go all moved together. The DOLT_RESET measurement has a failing control (2.3.1 8/150), so it counts.
  • 65290cca — tools/nogo tidy is a no-op at this head. The durable fix (directories: ["/", "/tools/nogo"] in .github/dependabot.yml) is still worth doing so the next group does not need a hand commit; not blocking here.
  • Dep-bump probes at head, GOTOOLCHAIN=go1.26.7: go mod verify all modules verified; go mod tidy no-op on root and tools/nogo; -mod=readonly go build ./cmd/bd for linux/amd64 pure ok; moved set = the 18 group bumps plus dolt/go, go-mysql-server, vitess, jsonpath, grpc 1.83.1→1.83.2 and one new indirect, github.com/dolthub/file-locks v0.1.1, all moving together.

Blocker: Bazel / release cross-compile → CI Gate / Required — the FreeBSD release artifact no longer builds. Job 114396252108:

external/gazelle++go_deps+com_github_dolthub_file_locks/lock.go:142:12: undefined: sysUnlock
… lock.go:192:14: undefined: sysLock … lock.go:272:12: undefined: sysOpen
##[error]release cross-compilation failed for: freebsd/amd64

Not a Bazel artifact: with plain Go at this head, GOOS=freebsd GOARCH=amd64 CGO_ENABLED=0 go build ./cmd/bd fails with the same six symbols; the same command at main (225ed7f) passes, and linux/amd64 at this head passes. Cause: dolt/go at c6af56fead88 replaced dolthub/fslock with dolthub/file-locks (dolthub/dolt#11935, 2026-09-29), imported from go/libraries/utils/filesys/lock.go, store/nbs/* and store/blobstore/*, all on bd's import path (go mod why -m github.com/dolthub/file-locks: cmd/bd → dolt/go/libraries/utils/filesys → file-locks). file-locks@v0.1.1 has lock_unix.go under //go:build linux || darwin and lock_windows.go under windows; no file provides the three sys* functions for freebsd (android passes because GOOS=android satisfies the linux tag). freebsd amd64 is in scripts/ci/release-targets.txt and .goreleaser.yml ships bd-freebsd-amd64, so merging this would break the FreeBSD release, not just a CI lane.

The fix is one build tag upstream: lock_unix.go uses only unix.Flock and LOCK_EX/LOCK_NB/LOCK_UN/EINTR/EWOULDBLOCK, all of which golang.org/x/sys/unix v0.49.0 provides for freebsd (zsyscall_freebsd_amd64.go), so //go:build unix (or linux || darwin || freebsd) compiles. Routes, for the maintainer to pick:

  1. Upstream dolthub/file-locks widens the tag → dolt bumps its require → beads bumps dolt/go again. Correct and slow; the beads side of the dolt bump would then wait on two upstream releases.
  2. Beads-side go_deps.module_override patch on github.com/dolthub/file-locks (the gozstd_nocgo.patch mechanism in MODULE.bazel) fixes :release_cross, but .goreleaser.yml's go build does not see Bazel patches, so the goreleaser FreeBSD artifact would still fail; a replace to a patched fork covers both at the cost of a fork pin.
  3. Drop freebsd amd64 from release-targets.txt and .goreleaser.yml (and the README/release-notes text that promises FreeBSD). A product decision, not one a dependency PR should make silently.

Either way this PR cannot merge as-is: the required gate is red on a real break. I would land route 1 or 2 as its own commit on this branch (fast-forward again, as randy did) and re-run; with that green and the derivedid.go:217 note answered, I expect to approve.

Aside (not blocking, worth an issue): randy's observation that Update default.nix vendorHash printed "already matched" on a run where the Nix build failed for a non-hash reason holds at the workflow level: .github/workflows/update-vendor-hash.yml's Detect whether hash changed step is git diff --quiet -- default.nix, so any update-nix-vendorhash.sh exit that leaves the file unchanged is reported as a match. #5731 is adjacent (drift on non-dependabot PRs) but does not cover this false positive.

Probes: worktrees probe-7441 (27f754d) and probe-main-7441 (225ed7f); go1.26.7; GOFLAGS=-mod=readonly.

…e break

The driver v2.4.1 bump changes what `bd init` writes. Dolt 2.4 stores a
descending index column as descending, where earlier Dolt silently stored
it ascending, and migration 0010 declares compaction_snapshots'
idx_comp_snap_issue with created_at DESC. Dolt older than 2.4 refuses a
database holding such a table with "table has unknown fields" on every
write and on information_schema reads, so a database created by this
branch cannot be opened by a bd built against driver v2.2.0, which every
current release is. Measured with bd built from this branch and from main:
on a database the new binary created, the old one fails create, list,
update and close at the pre-open schema skew probe. A database the older
engine created keeps its ascending index and stays usable by both
binaries after the new engine writes to it, and an old bd running against
a dolt sql-server 2.4.1 already creates the descending index.

This is the root cause behind the "table has unknown fields" evidence the
RecommendedMin bump cites. Record it under [Unreleased], together with the
proxied-server recommendation and the stricter default sql_mode Dolt 2.4
reports, so the release notes say which databases are affected and which
binaries have to move together.

Agent-Signature: claude-agent-sdk-claude-opus-5-5-max on behalf of Julian Knutsen
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@bee-ghosttrack

Copy link
Copy Markdown
Collaborator

Re-read at head 261472ac (the changelog commit, nothing else moved since 27f754db). The 06:40Z REQUEST CHANGES stands; two things to add.

1. Blocker unchanged. Bazel / release cross-compile on this head (job 114409785146) fails on the same six symbols in external/gazelle++go_deps+com_github_dolthub_file_locks/lock.go (sysUnlock ×4, sysLock, sysOpen) for freebsd/amd64; CI Gate / Required is red on it. Routes 1–3 in the review above still apply; nothing in this push touches go.mod or the targets file.

2. The changelog's compatibility floor is three patch releases too high. The new entry says a database created by this release "can no longer be opened by Dolt older than 2.4", and attributes it to Dolt 2.4 storing a descending index column as descending (migration 0010's idx_comp_snap_issue (…, created_at DESC)). The mechanism is right, the version is not: that change is dolthub/dolt#11746 ("Added DESC indexes and NULL ordering", merged 2026-09-09), which shipped in Dolt 2.3.3 (2026-09-09), not 2.4.0. Measured against a database bd init wrote with this head's binary (embedded, .beads/embeddeddolt/pb), one fresh copy per CLI:

dolt CLI SELECT COUNT(*) FROM information_schema.tables CREATE TABLE+INSERT SELECT … FROM compaction_snapshots
2.2.0 table has unknown fields same same
2.3.1 table has unknown fields same same
2.3.2 table has unknown fields same same
2.3.3 113 ok 0 rows; SHOW CREATE shows created_at DESC
2.3.5 113 ok same

So the PR's own measurement (2.2.0 and 2.3.1 fail, 2.4.1 passes, per policy.go and install-dolt.sh) is correct but the bracket it supports is "older than 2.3.3", and the entry's "any database whose schema a dolt sql-server 2.4 or newer created" is likewise 2.3.3 or newer. Keeping RecommendedMin at 2.4.1 is still the right recommendation (2.3.x carries the DOLT_RESET regression the pin comment measures), but the changelog is the sentence users will quote when a 2.3.3–2.3.5 server opens the workspace fine. A one-word fix in the same paragraph; please fold it into the next push rather than a separate commit.

The derivedid.go:217 note from the review is still open.

Probes: worktree probe-7441 at 261472ac, go1.26.7, -mod=readonly; dolt 2.2.0/2.3.1 from the local measurement cache, 2.3.2/2.3.3 from the GitHub release tarballs (dolt-darwin-arm64), 2.3.5 the local install.

@gascityinc-randy

Copy link
Copy Markdown
Contributor

Correction to the scope in my earlier comment, from a deeper review (CHANGELOG entry in 261472a):

  • Only databases first created under Dolt ≥ 2.4 are affected. Dolt 2.4 stores the created_at DESC column of idx_comp_snap_issue (migration 0010) as a real descending index. Older Dolt (bd releases on driver 2.2.0, dolt CLI 2.2.0/2.3.1) then fails with table has unknown fields. Databases created earlier keep an ascending index and stay usable by old and new bd in both directions. Maintainers accepted this as a one-way change.
  • The stricter default sql_mode applies in embedded mode too, not only server mode. Zero dates and 1/0 behave the same on 2.2.0 and 2.4.1.
  • Remaining blocker: the freebsd/amd64 cross-compile needs dolthub/file-locks v0.1.2 (upstream build-tag fix pending).

@bee-ghosttrack

Copy link
Copy Markdown
Collaborator

On the "file-locks v0.1.2 (upstream build-tag fix pending)" line above, for the record as of 2026-10-11T07:22:42Z: dolthub/file-locks has no v0.1.2 tag (latest v0.1.1, 56115ae1), no open or merged PR since #4 on 2026-09-24, and dolthub/file-locks#5 (the build-tag report) has no reply yet. Nothing is pending upstream that this PR can wait on without someone opening that PR; routes 1–3 in the review stand.

quad341 pushed a commit to versioned-beads/beads that referenced this pull request Oct 11, 2026
Resolve Dependabot alerts gastownhall#146 (apache/thrift < 0.24.0) and gastownhall#151
(google.golang.org/grpc <= 1.83.1) on the root module with the minimal
bump: no other module moves, and both need only go 1.25, so the Nix
flake stays on its current nixpkgs. Recompute default.nix vendorHash
for the new go.sum.

This lands the security fix independently of the Dolt 2.4.1 upgrade
in gastownhall#7441, which carries the same two bumps.

Co-authored-by: Julian Knutsen <julianknutsen@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@shrisha

shrisha commented Oct 15, 2026

Copy link
Copy Markdown

Here are some real-world numbers for this bump, and a PR for the freebsd blocker.

Why it matters for us. We use bd 1.2.2 in embedded mode, syncing through a git+ssh remote on GitHub. The Dolt store in refs/dolt/data is about 1 GiB. The embedded Dolt (2026-06-05) has both git-remote bugs this pin fixes: dolthub/dolt#11949, where each process deletes its fetch ref so every pull re-downloads the whole store, and #11916, where each ranged read re-inflates a 50 MiB part. Pulling one new bead takes about 30 s against GitHub, and older clones run past 12 minutes. A profile of one 30 s pull put 28.4 s in a single git fetch of refs/dolt/data.

A/B test at this PR's head (261472ac). Two fresh clones point at a local bare mirror of our real refs/dolt/data (no network). Clone A pushes 1, 3 and then 5 beads, and clone B pulls after each push. Both binaries ran the same harness:

bd 1.2.2 this head
B's bd dolt pull, rounds 1/2/3 10.2 / 10.3 / 10.4 s 2.7 / 2.5 / 2.5 s
B's git cache across a pull 633 MB → 1.5 GB, every round 639 → 640 MB
refs in the cache after a pull none refs/dolt/remotes/origin/dolt/data/last
most cat-file blob calls on one OID 39 → 110 → 184 2
beads received 9/9 9/9

The persistent anchor ref from dolthub/dolt#11991 survives between processes as intended, and the repeated re-reads are gone. Against GitHub, the old binary's per-pull cost is a full ~1 GiB transfer, so the real-world gap is larger than these local-mirror numbers.

The freebsd cross-compile. I've opened dolthub/file-locks#6 for dolthub/file-locks#5. It restores the build constraint dolthub/fslock had (darwin || dragonfly || freebsd || linux || netbsd || openbsd), not unix, because unix fails on aix. The test suite passes on real FreeBSD 15.1 and OpenBSD 7.9 VMs. With that branch swapped in through a go.work, GOOS=freebsd GOARCH=amd64 CGO_ENABLED=0 go build -tags gms_pure_go ./cmd/bd at this head builds; with v0.1.1 it fails on undefined: sysOpen. I've asked for a v0.1.2 tag. Once it exists, a github.com/dolthub/file-locks v0.1.2 line in beads' go.mod should clear Bazel / release cross-compile without waiting for a Dolt release, since MVS picks it over Dolt's v0.1.1.

(This head is also CONFLICTING with main again, so it will need bringing forward either way.)

Prepared with the help of Claude Code. I ran and reviewed the measurements above.

@dependabot @github

dependabot Bot commented on behalf of github Oct 16, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Oct 16, 2026
@dependabot
dependabot Bot deleted the dependabot/go_modules/go-deps-2621e3d13d branch October 16, 2026 20:44
gascity-eddie Bot pushed a commit that referenced this pull request Oct 18, 2026
…e break

The driver v2.4.1 bump changes what `bd init` writes. Dolt 2.4 stores a
descending index column as descending, where earlier Dolt silently stored
it ascending, and migration 0010 declares compaction_snapshots'
idx_comp_snap_issue with created_at DESC. Dolt older than 2.4 refuses a
database holding such a table with "table has unknown fields" on every
write and on information_schema reads, so a database created by this
branch cannot be opened by a bd built against driver v2.2.0, which every
current release is. Measured with bd built from this branch and from main:
on a database the new binary created, the old one fails create, list,
update and close at the pre-open schema skew probe. A database the older
engine created keeps its ascending index and stays usable by both
binaries after the new engine writes to it, and an old bd running against
a dolt sql-server 2.4.1 already creates the descending index.

This is the root cause behind the "table has unknown fields" evidence the
RecommendedMin bump cites. Record it under [Unreleased], together with the
proxied-server recommendation and the stricter default sql_mode Dolt 2.4
reports, so the release notes say which databases are affected and which
binaries have to move together.

Correction on re-landing: the descending-index storage change is
dolthub/dolt#11746, which shipped in Dolt 2.3.3, not 2.4.0 (bracketed by
bee-ghosttrack on #7441: dolt 2.3.2 fails, 2.3.3 and 2.3.5 open the
database). The entry now gives 2.3.3 as the compatibility floor and keeps
2.4.1 as the recommendation.

Agent-Signature: claude-agent-sdk-claude-opus-5-5-max on behalf of Julian Knutsen
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
gascityinc-randy Bot pushed a commit that referenced this pull request Oct 23, 2026
…e break

The driver v2.4.1 bump changes what `bd init` writes. Dolt 2.4 stores a
descending index column as descending, where earlier Dolt silently stored
it ascending, and migration 0010 declares compaction_snapshots'
idx_comp_snap_issue with created_at DESC. Dolt older than 2.4 refuses a
database holding such a table with "table has unknown fields" on every
write and on information_schema reads, so a database created by this
branch cannot be opened by a bd built against driver v2.2.0, which every
current release is. Measured with bd built from this branch and from main:
on a database the new binary created, the old one fails create, list,
update and close at the pre-open schema skew probe. A database the older
engine created keeps its ascending index and stays usable by both
binaries after the new engine writes to it, and an old bd running against
a dolt sql-server 2.4.1 already creates the descending index.

This is the root cause behind the "table has unknown fields" evidence the
RecommendedMin bump cites. Record it under [Unreleased], together with the
proxied-server recommendation and the stricter default sql_mode Dolt 2.4
reports, so the release notes say which databases are affected and which
binaries have to move together.

Correction on re-landing: the descending-index storage change is
dolthub/dolt#11746, which shipped in Dolt 2.3.3, not 2.4.0 (bracketed by
bee-ghosttrack on #7441: dolt 2.3.2 fails, 2.3.3 and 2.3.5 open the
database). The entry now gives 2.3.3 as the compatibility floor and keeps
2.4.1 as the recommendation.

Agent-Signature: claude-agent-sdk-claude-opus-5-5-max on behalf of Julian Knutsen
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
timothybrush pushed a commit to timothybrush/beads that referenced this pull request Oct 23, 2026
…bility fixes (gastownhall#7646)

* build(deps): bump the go-deps group across 1 directory with 20 updates

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

| Package | From | To |
| --- | --- | --- |
| [github.com/anthropics/anthropic-sdk-go](https://github.com/anthropics/anthropic-sdk-go) | `1.71.0` | `1.80.0` |
| [github.com/dolthub/driver/v2](https://github.com/dolthub/driver) | `2.2.0` | `2.4.1` |
| [github.com/gowebpki/jcs](https://github.com/gowebpki/jcs) | `1.0.1` | `1.0.2` |
| [go.opentelemetry.io/otel](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/exporters/stdout/stdoutmetric](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/exporters/stdout/stdouttrace](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/metric](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/sdk](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/sdk/metric](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [go.opentelemetry.io/otel/trace](https://github.com/open-telemetry/opentelemetry-go) | `1.46.0` | `1.47.0` |
| [golang.org/x/sync](https://github.com/golang/sync) | `0.23.0` | `0.24.0` |
| [golang.org/x/sys](https://github.com/golang/sys) | `0.48.0` | `0.49.0` |
| [golang.org/x/term](https://github.com/golang/term) | `0.46.0` | `0.47.0` |
| [github.com/charmbracelet/x/ansi](https://github.com/charmbracelet/x) | `0.11.8` | `0.11.9` |
| [github.com/dolthub/dolt/go](https://github.com/dolthub/dolt) | `0.40.5-0.20260806213044-796d07497741` | `0.40.5-0.20261002233748-c6af56fead88` |
| [github.com/dolthub/go-mysql-server](https://github.com/dolthub/go-mysql-server) | `0.20.1-0.20260805191915-e5eafe0da809` | `0.20.1-0.20261001232740-19405eb6f203` |
| [github.com/dolthub/vitess](https://github.com/dolthub/vitess) | `0.0.0-20260728212736-0542037326d7` | `0.0.0-20260930232419-a6b7b0c65d17` |
| [golang.org/x/mod](https://github.com/golang/mod) | `0.40.0` | `0.41.0` |
| [golang.org/x/net](https://github.com/golang/net) | `0.58.0` | `0.59.0` |

Updates `github.com/anthropics/anthropic-sdk-go` from 1.71.0 to 1.80.0
- [Release notes](https://github.com/anthropics/anthropic-sdk-go/releases)
- [Changelog](https://github.com/anthropics/anthropic-sdk-go/blob/main/CHANGELOG.md)
- [Commits](anthropics/anthropic-sdk-go@v1.71.0...v1.80.0)

Updates `github.com/dolthub/driver/v2` from 2.2.0 to 2.4.1
- [Release notes](https://github.com/dolthub/driver/releases)
- [Commits](dolthub/driver@v2.2.0...v2.4.1)

Updates `github.com/gowebpki/jcs` from 1.0.1 to 1.0.2
- [Release notes](https://github.com/gowebpki/jcs/releases)
- [Commits](gowebpki/jcs@v1.0.1...v1.0.2)

Updates `go.opentelemetry.io/otel` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/exporters/stdout/stdoutmetric` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/exporters/stdout/stdouttrace` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/metric` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/sdk` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/sdk/metric` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `go.opentelemetry.io/otel/trace` from 1.46.0 to 1.47.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go@v1.46.0...v1.47.0)

Updates `golang.org/x/sync` from 0.23.0 to 0.24.0
- [Commits](golang/sync@v0.23.0...v0.24.0)

Updates `golang.org/x/sys` from 0.48.0 to 0.49.0
- [Commits](golang/sys@v0.48.0...v0.49.0)

Updates `golang.org/x/term` from 0.46.0 to 0.47.0
- [Commits](golang/term@v0.46.0...v0.47.0)

Updates `github.com/charmbracelet/x/ansi` from 0.11.8 to 0.11.9
- [Commits](charmbracelet/x@ansi/v0.11.8...ansi/v0.11.9)

Updates `github.com/dolthub/dolt/go` from 0.40.5-0.20260806213044-796d07497741 to 0.40.5-0.20261002233748-c6af56fead88
- [Release notes](https://github.com/dolthub/dolt/releases)
- [Commits](https://github.com/dolthub/dolt/commits)

Updates `github.com/dolthub/go-mysql-server` from 0.20.1-0.20260805191915-e5eafe0da809 to 0.20.1-0.20261001232740-19405eb6f203
- [Release notes](https://github.com/dolthub/go-mysql-server/releases)
- [Commits](https://github.com/dolthub/go-mysql-server/commits)

Updates `github.com/dolthub/vitess` from 0.0.0-20260728212736-0542037326d7 to 0.0.0-20260930232419-a6b7b0c65d17
- [Commits](https://github.com/dolthub/vitess/commits)

Updates `golang.org/x/mod` from 0.40.0 to 0.41.0
- [Commits](golang/mod@v0.40.0...v0.41.0)

Updates `golang.org/x/net` from 0.58.0 to 0.59.0
- [Commits](golang/net@v0.58.0...v0.59.0)

---
updated-dependencies:
- dependency-name: github.com/anthropics/anthropic-sdk-go
  dependency-version: 1.80.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/dolthub/driver/v2
  dependency-version: 2.4.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/gowebpki/jcs
  dependency-version: 1.0.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/exporters/stdout/stdoutmetric
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/exporters/stdout/stdouttrace
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/metric
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/sdk
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/sdk/metric
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/otel/trace
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: golang.org/x/sync
  dependency-version: 0.24.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: golang.org/x/sys
  dependency-version: 0.49.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: golang.org/x/term
  dependency-version: 0.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/charmbracelet/x/ansi
  dependency-version: 0.11.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: github.com/dolthub/dolt/go
  dependency-version: 0.40.5-0.20261002233748-c6af56fead88
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: github.com/dolthub/go-mysql-server
  dependency-version: 0.20.1-0.20261001232740-19405eb6f203
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: github.com/dolthub/vitess
  dependency-version: 0.0.0-20260930232419-a6b7b0c65d17
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: golang.org/x/mod
  dependency-version: 0.41.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: golang.org/x/net
  dependency-version: 0.59.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
(cherry picked from commit 1a1fd25)

* build(nix): move the flake to nixos-26.05 for go 1.26.5+

dolthub/driver v2.4.1 declares go 1.26.5, but nixos-25.11 is frozen
(last commit 2026-06-30) at go 1.26.4. default.nix's postPatch can only
lower the root module's go directive, not a dependency's, so the Nix
build failed with "requires go >= 1.26.5 (running go 1.26.4;
GOTOOLCHAIN=local)". nixos-26.05 ships go 1.26.8 and keeps
buildGo126Module and go_1_26, and the weekly flake-lock update can
track it.

Recompute vendorHash for the bumped go.sum.

Verified with nixos/nix: nix flake check passes, nix run .#default --
--help works, and the devShell reports go1.26.8.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* build(nogo): align tools/nogo x/mod, x/sync, x/text with the root module

TestModuleRequirementsAgreeWithRoot (//tools/nogo:nogo_test) requires
the analyzer module's shared requirements to match go.mod. The go-deps
bump moved the root to x/mod v0.41.0, x/sync v0.24.0 and x/text v0.42.0.

After the rebase onto main, gastownhall#6355 had already raised tools/nogo to
x/mod v0.41.0 and x/text v0.42.0, so this commit now moves only x/sync.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* fix(storage): compute the next version revision with a scalar subquery

go-mysql-server's aggregate-over-index rewrite
(dolthub/go-mysql-server#3907, pulled in by the driver v2.4.1 bump)
returns zero rows, not one NULL row, for an ungrouped MAX/MIN over an
empty primary-key prefix:

  SELECT COALESCE(MAX(revision), 0) + 1 FROM issue_versions WHERE issue_id = ?

so every first mint on an issue failed with "versioned history: compute
next revision for X: sql: no rows in result set", breaking the
versioned-history contract tests on the embedded, served, server and UoW
tiers. Wrap the aggregate in a scalar subquery: the outer SELECT has no
FROM and yields exactly one row on every engine, including dolt 2.2.0.

This is the only production query with the affected shape; other
MAX/MIN uses are grouped, unfiltered, range-filtered, or on a secondary
index. Versioned history is only enabled in tests today, so no release
is affected.

Add TestEmbeddedFirstMintOnEmptyHistoryIsRevisionOne, which fails on the
old query and pins that the first mint is revision 1 and the second 2.

Main's gastownhall#6661 pins the old mint SQL in two sqlmock expectations
(version_history_preenable_scan_test.go); move both to the
scalar-subquery literal, and name recordVersionAtInTx, where the read now
lives, in the single-writer comment.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* build(dolt): raise the Dolt CLI, container and Bazel pins to 2.4.1

Carry gastownhall#7254's pin bump onto the driver v2.4.1 upgrade. The pinned
dolt 2.2.0 CLI cannot write storage the 2.4.1 engine created: after a
`bd init` through driver v2.4.1, `dolt sql -q "INSERT ..."` fails with
"table has unknown fields" on dolt 2.2.0 and 2.3.1 and succeeds on
2.4.1. That broke the protocol, proxied and TestEmbeddedInit* lanes
wherever a test shells out to `dolt sql`.

The pin policy in install-dolt.sh / dolt.md requires the DOLT_RESET
('--hard') measurement before raising the pin. Measured 2026-10-10:
2.3.1 8/150 broken (positive control), 2.4.1 0/250 over two runs, the
embedded engine via driver v2.4.1 0/60. The docs keep the 2.3.x rows and
the "raise only once measured" rule and add the 2.4.1 row.

- install-dolt.sh, pull-dolt-image.sh, testdoltcommon.go, dolt.bzl
  (DOLT_VERSION plus release digests; linux-amd64 re-hashed locally) and
  the script test constants move to 2.4.1.
- doltversion.RecommendedMin is 2.4.1, documented with the unknown-fields
  evidence; it stays a recommendation, not a hard floor.
- Three fixes gastownhall#7254 lacked: the doltversion cache tests derive their
  "recent version" stub from RecommendedMin instead of 2.1.0 (now below
  the minimum, which failed the Windows lane); the server fingerprint
  golden takes dolt 2.4.x's default sql_mode; and doltSQLServerImage in
  scripts/repo_helpers_test.go, where main moved it from
  pull_dolt_image_test.go.
- Refresh comments that called 2.2.0 the current CLI pin.

Release note: managed proxied-server mode now recommends dolt >= 2.4.1,
and server-mode users on dolt 2.4.x get the stricter default sql_mode
(adds NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO).

Co-authored-by: coffeegoddd <dustin@dolthub.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* docs(changelog): note the Dolt 2.4.1 engine's descending-index storage break

The driver v2.4.1 bump changes what `bd init` writes. Dolt 2.4 stores a
descending index column as descending, where earlier Dolt silently stored
it ascending, and migration 0010 declares compaction_snapshots'
idx_comp_snap_issue with created_at DESC. Dolt older than 2.4 refuses a
database holding such a table with "table has unknown fields" on every
write and on information_schema reads, so a database created by this
branch cannot be opened by a bd built against driver v2.2.0, which every
current release is. Measured with bd built from this branch and from main:
on a database the new binary created, the old one fails create, list,
update and close at the pre-open schema skew probe. A database the older
engine created keeps its ascending index and stays usable by both
binaries after the new engine writes to it, and an old bd running against
a dolt sql-server 2.4.1 already creates the descending index.

This is the root cause behind the "table has unknown fields" evidence the
RecommendedMin bump cites. Record it under [Unreleased], together with the
proxied-server recommendation and the stricter default sql_mode Dolt 2.4
reports, so the release notes say which databases are affected and which
binaries have to move together.

Correction on re-landing: the descending-index storage change is
dolthub/dolt#11746, which shipped in Dolt 2.3.3, not 2.4.0 (bracketed by
bee-ghosttrack on gastownhall#7441: dolt 2.3.2 fails, 2.3.3 and 2.3.5 open the
database). The entry now gives 2.3.3 as the compatibility floor and keeps
2.4.1 as the recommendation.

Agent-Signature: claude-agent-sdk-claude-opus-5-5-max on behalf of Julian Knutsen
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* fix(deps): move go-runewidth to v0.0.28 to drop a 35 ms init from every bd run

The go-deps group's charmbracelet/x/ansi v0.11.9 requires
mattn/go-runewidth v0.0.27. In v0.0.26 and v0.0.27 that package
fills a 2 MB width table eagerly in init (mattn/go-runewidth#104), and bd
links it through lipgloss, bubbles and dolt's tabular printer, so every bd
command paid for it before main ran:

  GODEBUG=inittrace=1 bd version   go-runewidth init 33-36 ms (v0.0.27),
                                   0.03-0.04 ms (v0.0.28),
                                   0.12-0.17 ms (main's v0.0.24)
  bd version wall time, median of 40: 147 ms (v0.0.27), 103 ms (v0.0.28),
                                      101 ms (main's v0.0.24)

v0.0.28 builds the table lazily (mattn/go-runewidth#105) and changes
nothing else that is observable: RuneWidth over all 1,114,112 code points
in all four EastAsianWidth/StrictEmojiNeutral combinations, and StringWidth
and Truncate over an emoji, flag, ZWJ, Indic and Hangul sample, are
byte-identical to v0.0.27. go-runewidth is an indirect dependency, so
Dependabot will not move it on its own.

TestTerminalStackPackageInitStaysUnderBudget re-executes the internal/ui
test binary with GODEBUG=inittrace=1 and fails when any package in the
terminal rendering stack spends more than 10 ms in init, taking the fastest
of three starts with GOGC=off so a garbage collection inside one init is not
billed to it. On v0.0.27 it fails naming go-runewidth (32 ms, 381 ms under
-race); on v0.0.28 every package is under 1.1 ms, and it passed 40 -race and 50
plain repetitions, then 30 of each with 24 busy-loop processes running.

Recompute default.nix's vendorHash with a fake-hash build in nixos/nix;
nix run .#default -- --help and nix flake check pass with it.

Agent-Signature: claude-agent-sdk-claude-opus-5-5-max on behalf of Julian Knutsen
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* docs(dolt): name 2.3.3 as the write boundary and drop the stale 2.3.x DOLT_RESET claim

The CHANGELOG entry gave a wrong reason to prefer 2.4.1 over 2.3.x: it said
the 2.3.x releases that can open a new database carry the
DOLT_RESET('--hard') regression. That regression is dolthub/dolt#11581,
fixed by dolthub/dolt#11652, which first shipped in 2.3.2, before the
2.3.3 write boundary. The reasons that do hold are that 2.4.1 is the
release CI pins and measured, and that releases before 2.4.0 mis-plan a
lookup join whose ON clause has an OR over indexed columns
(dolthub/dolt#11886, fixed by go-mysql-server#3899, the cause of gastownhall#7037):
dolt 2.3.5 pins a go-mysql-server without that fix, and 2.4.0 pins one
with it.

The surrounding text this branch added also implied a later boundary than
the real one:

- troubleshooting.md said storage the v2.4.1 engine writes "is not
  writable by older dolt CLIs" and that "2.3.x carries" the DOLT_RESET
  defect. Re-measured 2026-10-17 against a database bd init created with
  this branch: dolt 2.2.0 and 2.3.2 fail a plain INSERT and an
  information_schema read with "table has unknown fields"; 2.3.3, 2.4.0
  and 2.4.1 succeed, and SHOW CREATE TABLE reports created_at DESC on
  idx_comp_snap_issue. The release tarballs match GitHub's asset digests.
- dolt.md and RecommendedMin's comment named only the two failing
  versions measured on 2026-10-10. Both now name 2.3.3 and
  dolthub/dolt#11746 (merged into 2.3.3, absent from 2.3.2), and the
  comment says why the recommendation is still 2.4.1.
- dolt.md said "Versions after 2.4.1 have not been measured", which
  implied 2.3.2 through 2.4.0 had been. None of them is in that table.
- The CHANGELOG put the stricter default sql_mode on "Dolt 2.4.1
  servers". SELECT @@GLOBAL.sql_mode in a fresh dolt init: 2.2.0 and 2.3.2
  report NO_ENGINE_SUBSTITUTION,ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES;
  2.3.3, 2.4.0 and 2.4.1 add NO_ZERO_IN_DATE, NO_ZERO_DATE and
  ERROR_FOR_DIVISION_BY_ZERO. It now says 2.3.3 and later.

RecommendedMin stays 2.4.1, and TestPinnedDoltCLIAtLeastRecommendedMin
still holds against the 2.4.1 pins.

Agent-Signature: claude-agent-sdk-claude-opus-5-5-max on behalf of Julian Knutsen
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* build(deps): bump dolthub/file-locks to v0.1.2 for BSD builds

file-locks v0.1.1 (pulled in transitively by Dolt 2.4.1) had no build
tags for freebsd/openbsd/netbsd/dragonfly, so the freebsd/amd64 release
cross-compile failed. dolthub/file-locks#6 (by @shrisha) adds them and
ships in v0.1.2.

Only file-locks moves in go.mod/go.sum; tools/nogo is unaffected. The
Nix vendorHash is recomputed for the new module set.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* build(deps): run the embedded Dolt engine on 2.5.1

Raise the direct requirements on github.com/dolthub/dolt/go,
go-mysql-server and vitess to the exact Dolt v2.5.1 release set and keep
the tagged github.com/dolthub/driver/v2 v2.4.1:

  dolthub/dolt/go        v0.40.5-0.20261020191035-d1f8f8e76386 (v2.5.1 tag)
  dolthub/go-mysql-server v0.20.1-0.20261016230655-239e0ad6b2f9
  dolthub/vitess          v0.0.0-20261014211039-3e903c0f05d3
  dolthub/jsonpath        follows (indirect)

No driver release exists on 2.5.x, and driver main now declares go
1.27.3, which would move every toolchain pin. The driver changed no Go
source between v2.4.1 and its 2.5-era commit (89f53f8d3f72), only
go.mod/go.sum, so this pairing is source-identical to DoltHub's own
driver build, on the release commit and with no replace directive.
dolt/go 2.5.1 says go 1.26.2, so the go directive is unaffected, and no
new module enters the graph.

Dolt 2.5.0 fixes the engine bug the scalar-subquery mint read works
around (dolthub/dolt#12093: 2.4.0 through 2.4.2 return no row for an
ungrouped MAX or MIN over an unmatched primary-key prefix) and the
replaceAgg panic on an ungrouped MAX of a non-key column under a fully
bound primary key (dolthub/go-mysql-server#4037). The workaround stays
for server-mode users on dolt 2.4.0 through 2.4.2.

Measured on this engine: the embedded tier's per-test outcome is
identical to the 2.4.1 engine (1755 pass, 59 skip), the default
sql_mode is unchanged, and the storage floor stays Dolt 2.3.3.

default.nix: vendorHash for the new go.sum. The example modules replace
github.com/steveyegge/beads with the repo root, so they follow its
requirements: go mod tidy in examples/library-usage and
examples/bd-example-extension-go (driver v2.4.1, dolthub/file-locks
v0.1.2, the go-deps group and this engine). Without it
scripts/build-examples.sh fails with "updates to go.mod needed"; this
was a review finding from gastownhall#7646's adoption review, re-applied here.

Agent-Signature: claude-agent-sdk-claude-opus-5-5-unknown-reasoning on behalf of Julian Knutsen
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* build(dolt): move the CLI, container and Bazel pins to 2.5.1 and recommend 2.5.0

The Dolt CLI pin (scripts/ci/install-dolt.sh), the test container
(dolthub/dolt-sql-server:2.5.1 in testdoltcommon.go and
pull-dolt-image.sh), the hermetic Bazel dolt (tools/bazel/dolt.bzl
DOLT_VERSION plus the four release-asset digests) and the docs snippet
move to 2.5.1, the release the embedded engine now links, so the CLI,
the container and embedded mode run the same Dolt.
TestPinnedDoltCLIMatchesContainerImage, TestPinnedDoltCLIAtLeastRecommendedMin
and test/docsync's doltpin test hold those in step.

2.5.1 passes the pin criterion install-dolt.sh states: measured
2026-10-21 by creating fresh databases and immediately calling
CALL DOLT_RESET('--hard'), 2.5.0 and 2.5.1 broke 0/500 each, 2.4.2
0/250 and the embedded 2.5.1 engine 0/100, against a 2.3.1 positive
control of 4/300. TestDoltServerFingerprint matches the existing golden
on the 2.5.1 CLI and container: the default sql_mode did not change
from 2.4.1.

doltversion.RecommendedMin moves to 2.5.0, the first release that
answers an ungrouped MAX or MIN over an unmatched primary-key prefix
with one NULL row (dolthub/dolt#12093; 2.4.0 through 2.4.2 return no
row, and panic on dolthub/go-mysql-server#4037). The old-version
warning now names what goes wrong below it, release range by range:
2.4.0-2.4.2 and #12093, the join mis-plan before 2.4.0
(dolthub/dolt#11886), the DOLT_RESET('--hard') regression on 2.3.0
and 2.3.1, and "table has unknown fields" before 2.3.3, the storage
floor. TestWarningMessage pins each clause. It stays a warning, not a
refusal. The scoped warning was a gastownhall#7646 adoption-review finding,
re-worded here for 2.5.0 and without migration 0071.

Agent-Signature: claude-agent-sdk-claude-opus-5-5-unknown-reasoning on behalf of Julian Knutsen
Co-authored-by: Eddie the Engineer <338826946+gascity-eddie[bot]@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* docs(code): correct the parity-oracle and port-check comments for the 2.5.1 pin

Review fixes from gastownhall#7646's adoption review, iterations 1-3, re-applied
without migration 0071 (they were carried by 2068dbe, which this
branch drops):

- cli_migrations.go puts the parity oracle's green run against the
  then-pinned 2.2.0 sql-server in the past tense. A 2.3.0-or-newer CLI
  executes the prepared ALTER, so with the CLI pinned at 2.5.1
  TestCLIBundleMatchesRuntimeCommittedSchema cannot catch a dropped
  override (re-probed 2026-10-21: a prepared ADD COLUMN vanishes on the
  2.2.0 CLI and lands on 2.5.1). The comment names the two binary-free
  tests that still can.
- localdoltserver.go's port comment covers 2.4.1 and 2.5.1 as well as
  2.2.0: each prints "Port N already in use." on a held port (2.5.1
  measured 2026-10-23).

Agent-Signature: claude-agent-sdk-claude-opus-5-5-unknown-reasoning on behalf of Julian Knutsen
Co-authored-by: Eddie the Engineer <338826946+gascity-eddie[bot]@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* test(storage): pin per-issue first-mint revisions

TestEmbeddedFirstMintOnEmptyHistoryIsRevisionOne now also creates a
second issue and pins that its first mint is revision 1: revisions
count per issue. On its own this kills a mutant that drops the
issue_id filter from the scalar subquery (the second issue then
continues the first issue's sequence: "first mint revision for a
second issue = 3, want 1").

A gastownhall#7646 adoption-review finding (iteration 1, gap 2), carried by
2068dbe and re-applied here without migration 0071.

Agent-Signature: claude-agent-sdk-claude-opus-5-5-unknown-reasoning on behalf of Julian Knutsen
Co-authored-by: Eddie the Engineer <338826946+gascity-eddie[bot]@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* docs(dolt): Dolt 2.5 version table; the descending-index change is one-way (floor 2.3.3)

Maintainer decision on gastownhall#7646: the descending-index storage change is
accepted as one-way. Dolt 2.3.3 and later store migration 0010's
created_at DESC on compaction_snapshots' idx_comp_snap_issue as
descending (dolthub/dolt#11746), and Dolt older than 2.3.3 cannot read
such a table ("table has unknown fields"). bd does not convert the index
back, so every database bd creates from this release on needs Dolt 2.3.3
or newer, and a bd built on it, for good. Databases created earlier keep
an ascending index and stay readable and writable by older Dolt even
after this release migrates and writes to them (measured 2026-10-21 with
Dolt 2.2.0 and 2.3.2).

- CHANGELOG: the entry now says the embedded engine is Dolt 2.5.1
  (driver v2.4.1 with dolt/go at the v2.5.1 release), that the change is
  one-way, that the recommended dolt is 2.5.0 (CI pins 2.5.1), and lists
  the defects below it: dolthub/dolt#12093 on 2.4.0-2.4.2, the join bug
  before 2.4.0, the DOLT_RESET('--hard') regression on 2.3.0 and 2.3.1.
- docs/architecture/dolt.md: the pin paragraph says embedded mode links
  the 2.5.1 engine and the CLI pin tracks it; a one-way statement; and
  one version table merging the DOLT_RESET measurements with the
  2.3.3 storage floor and the MAX/MIN engine bug (2.4.0-2.4.2 failing,
  2.5.0 and later correct; 2026-10-21: 2.3.1 4/300, 2.5.0 and 2.5.1
  0/500 each, 2.4.2 0/250).
- troubleshooting.md: the old-version warning section recommends 2.5.0
  and lists the three defect ranges, pointing at dolt.md.
- scripts/test-git-remote.sh: dolt >= 2.3.3. Its 2.2.0 floor rested on
  migration 0071, which this branch does not carry.
- sync-setup.md scopes the DOLT_RESET regression to 2.3.0 and 2.3.1
  (2.3.2 carries the fix); upgrading.md scopes the gastownhall#7037 embedded-engine
  caveat to bd releases that link Dolt older than 2.4.0.

The MAX/MIN column is bee-ghosttrack's reproduction from gastownhall#7646.

Agent-Signature: claude-agent-sdk-claude-opus-5-5-unknown-reasoning on behalf of Julian Knutsen
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Julian Knutsen <julianknutsen@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-authored-by: coffeegoddd <dustin@dolthub.com>
Co-authored-by: Eddie the Engineer <338826946+gascity-eddie[bot]@users.noreply.github.com>
rjgeng pushed a commit to rjgeng/beads that referenced this pull request Oct 23, 2026
Resolve Dependabot alerts gastownhall#146 (apache/thrift < 0.24.0) and gastownhall#151
(google.golang.org/grpc <= 1.83.1) on the root module with the minimal
bump: no other module moves, and both need only go 1.25, so the Nix
flake stays on its current nixpkgs. Recompute default.nix vendorHash
for the new go.sum.

This lands the security fix independently of the Dolt 2.4.1 upgrade
in gastownhall#7441, which carries the same two bumps.

Co-authored-by: Julian Knutsen <julianknutsen@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
(cherry picked from commit 7477ec1)

Backport note: hotfix/1.3.1 was on grpc v1.83.0 (main was on v1.83.1),
so go.mod/go.sum were re-resolved with `go get google.golang.org/grpc@v1.83.2
github.com/apache/thrift@v0.24.0 && go mod tidy`; no other module moved.
default.nix vendorHash recomputed for this go.sum with a nixos/nix build.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Dependency updates go Go code and modules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants