Skip to content

auto-docs: Update Go modules#379

Open
vbotbuildovich wants to merge 1 commit into
mainfrom
update-go-mod
Open

auto-docs: Update Go modules#379
vbotbuildovich wants to merge 1 commit into
mainfrom
update-go-mod

Conversation

@vbotbuildovich
Copy link
Copy Markdown
Contributor

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

@netlify
Copy link
Copy Markdown

netlify Bot commented May 21, 2026

Deploy Preview for docs-ui ready!

Name Link
🔨 Latest commit d43ab7c
🔍 Latest deploy log https://app.netlify.com/projects/docs-ui/deploys/6a21f1a065fd7400084a2c70
😎 Deploy Preview https://deploy-preview-379--docs-ui.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 28 (🔴 down 5 from production)
Accessibility: 89 (no change from production)
Best Practices: 92 (no change from production)
SEO: 88 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 21, 2026

Review Change Stack

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e0a1b612-4523-4d7e-b51a-16f316db5cc2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

This 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 github.com/redpanda-data/benthos/v4 and github.com/redpanda-data/connect/v4 are bumped to newer versions, and numerous indirect dependencies are updated, including protobuf utilities, compression libraries, JSON utilities, parquet support, logging frameworks, OpenTelemetry modules, and several golang.org/x packages.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

  • redpanda-data/docs-ui#303: Modifies blobl-editor/wasm/go.mod by bumping github.com/redpanda-data/connect/v4 dependency versions.
  • redpanda-data/docs-ui#324: Updates blobl-editor/wasm/go.mod with version bumps to benthos/v4 and connect/v4 direct dependencies.
  • redpanda-data/docs-ui#354: Updates the same file with Go toolchain directive and direct dependency version changes for benthos and connect modules.

Suggested reviewers

  • JakeSCahill
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'auto-docs: Update Go modules' is clearly related to the changeset, which updates Go module dependencies in blobl-editor/wasm/go.mod.
Description check ✅ Passed The description 'This PR updates the Go modules for the Bloblang playground Wasm code' is directly related to the changeset, which updates Go module versions in blobl-editor/wasm/go.mod.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch update-go-mod

Comment @coderabbitai help to get the list of available commands and usage tips.

@vbotbuildovich vbotbuildovich force-pushed the update-go-mod branch 2 times, most recently from c06de4a to a40137c Compare May 29, 2026 17:02
Copy link
Copy Markdown
Contributor

@Feediver1 Feediver1 left a comment

Choose a reason for hiding this comment

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

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/crypto 0.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 by jhump/protoreflect/v2)

Critical issues

None.

Things worth noting (not blockers)

  1. 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.

  2. Two pseudo-versions added (no real semver tag): nsf/jsondiff v0.0.0-20260207060731-... and petermattis/goid v0.0.0-20260226131333-.... Standard Go practice for unreleased deps, but harder to audit than tagged releases. The petermattis/goid add 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.

  3. 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-playground check 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

  1. Manual sanity-test the playground against the deploy preview. Try a Bloblang expression that exercises something potentially non-trivial (e.g., a protobuf decode/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. 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.

  3. 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 diff summary of which deps moved by major/minor/patch. Out of scope here.

Impact on other files

  • No .adoc changes — this only touches the WASM build artifact's dependency manifest.
  • Bloblang playground rendering on docs.redpanda.com will 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants