auto-docs: Update Go modules#379
Conversation
✅ Deploy Preview for docs-ui ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThis PR updates the Go module file for blobl-editor's WASM package, advancing the Go toolchain from version 1.25.6 to 1.26.3. The direct dependencies Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
c06de4a to
a40137c
Compare
Feediver1
left a comment
There was a problem hiding this comment.
Docs standards review (Bloblang playground WASM dep update)
Files reviewed: 2 (blobl-editor/wasm/go.mod, blobl-editor/wasm/go.sum). Not an .adoc content PR — this is an automated dependency-update bot PR for the Bloblang playground's WASM build.
What this PR does
Routine Go-modules sync for the Bloblang playground WASM. Key bumps:
- Go runtime: 1.25.6 → 1.26.3
redpanda-data/benthos/v4: v4.63.1 → v4.73.0 (10 minor versions)redpanda-data/connect/v4: v4.78.0 → v4.94.1 (16 minor versions — significant jump that brings the playground's runtime in line with the current Connect release we've been documenting in rp-connect-docs)- Many indirect dep bumps (mostly patch-level): OpenTelemetry 1.39 → 1.43,
golang.org/x/crypto0.46 → 0.52,klauspost/compress,apache/thrift,parquet-go/parquet-go, etc. - New indirect deps added:
jhump/protoreflect/v2 v2.0.0-beta.2,parquet-go/bitpack,parquet-go/jsonlite,petermattis/goid,twpayne/go-geom - Removed:
bufbuild/protocompile(apparently replaced byjhump/protoreflect/v2)
Critical issues
None.
Things worth noting (not blockers)
-
One beta dependency introduced as indirect:
github.com/jhump/protoreflect/v2 v2.0.0-beta.2. This is a transitive dep (not chosen by this PR), but worth flagging that the playground now depends on a beta-grade protocol-reflection library. If the playground starts misbehaving on protobuf-related Bloblang operations, this is a candidate to investigate first. -
Two pseudo-versions added (no real semver tag):
nsf/jsondiff v0.0.0-20260207060731-...andpetermattis/goid v0.0.0-20260226131333-.... Standard Go practice for unreleased deps, but harder to audit than tagged releases. Thepetermattis/goidadd is new — it's typically used for mutex/goroutine debugging instrumentation, and as a transitive its appearance probably tracks an upstream change in benthos or connect. -
16 minor versions of Connect in one PR is a large jump. The bot is catching up after a long gap (PR opened 2026-05-21, almost 2 weeks ago). If anything in benthos's Bloblang semantics changed between v4.63 and v4.73, this is the PR that introduces it. The
test-bloblang-playgroundcheck passes, so at minimum the playground still runs — but it's the kind of change worth a quick manual test against a known-tricky Bloblang expression before merge.
Suggestions
-
Manual sanity-test the playground against the deploy preview. Try a Bloblang expression that exercises something potentially non-trivial (e.g., a
protobufdecode/encode, an Iceberg-relevant transform, a date math expression) and confirm output matches expectations. The CI test covers the existence/build of the WASM bundle but probably not deep semantics across the dep upgrade window. -
2-week-old bot PR without review is a process smell. Bot PRs that update production-facing components (the Bloblang playground is user-facing on
docs.redpanda.com) should probably auto-merge after a window of green CI, OR get human triage on a known cadence. Worth raising as a separate process discussion — not in scope to fix in this PR. -
No PR description detail beyond "This PR updates the Go modules for the Bloblang playground Wasm code" is fine for a routine bot PR. If you want richer auditing, the bot could include a
git diffsummary of which deps moved by major/minor/patch. Out of scope here.
Impact on other files
- No
.adocchanges — this only touches the WASM build artifact's dependency manifest. - Bloblang playground rendering on
docs.redpanda.comwill use the updated WASM after merge + UI bundle rebuild. Worth eyeballing the playground page once this lands to confirm no regression in basic interactivity. - No nav.adoc, xrefs, or content affected.
CodeRabbit findings
None — CodeRabbit doesn't typically post on go.sum diffs (too noisy, no signal).
What works well
test-bloblang-playground: SUCCESS— the WASM still compiles and the playground test suite passes against the new deps. This is the meaningful signal.- Routine, scoped, automated — bot only touched
go.mod/go.sum. No incidental drift into other files. - Connect at v4.94.1 matches recent rp-connect-docs work — keeping the playground's runtime aligned with current product is the right state.
Verdict
This is a routine dep-update PR that's been sitting too long. CI is green, the test suite exercises the WASM bundle, and the changes are all expected for a "catch up to current Connect" sweep. Probably safe to merge after a one-minute manual playground sanity check on the deploy preview. The 2-week gap without review is the more interesting concern — but that's a process question for bot PRs in general, not a defect in this one.
d43ab7c to
401784d
Compare
95bfb44 to
c59abb0
Compare
c59abb0 to
2ddf69a
Compare
2ddf69a to
7b6293d
Compare

This PR updates the Go modules for the Bloblang playground Wasm code.