Repository navigation
chore(deps): update test-tooling (9.6) - #8212
elastic-renovate-prod[bot] wants to merge 1 commit into
Conversation
elastic-renovate-prod
Bot
added
automation
backport-skip
elastic-renovate-prod
Bot
added
dependency
skip-changelog
Team:Elastic-Agent-Control-Plane
ℹ️ Artifact update noticeFile name: testing/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
There was a problem hiding this comment.
🟡 Changes recommended
The testing module requires Go 1.27 while E2E jobs remain pinned to Go 1.26.10, forcing automatic toolchain downloads or causing failures when toolchain switching is disabled.
1 open issue
What changed in this PR
Updates Fleet Server’s test-tooling dependencies on the 9.6 branch, including container orchestration and network fault-injection libraries.
Changes:
- Upgrades Toxiproxy to v2.13.0 and Testcontainers to v0.45.0.
- Refreshes transitive dependencies and module checksums.
- Raises the testing module’s minimum Go version from 1.26.10 to 1.27.0.
| File | Description |
|---|---|
testing/go.sum |
Updates checksums for upgraded dependencies and removes obsolete entries. |
testing/go.mod |
Updates test-tooling requirements and the minimum Go version. |
Review effort: Balanced
| module github.com/elastic/fleet-server/testing | ||
|
|
||
| go 1.26.10 | ||
| go 1.27.0 |
Dependency Update AnalysisSummary: This PR updates Go test-only dependencies in
|
| Check | Result |
|---|---|
| Breaking changes | ✅ None found for this repo usage |
| Testable in PR | ✅ Yes (Buildkite PR pipeline runs unit/integration/e2e) |
Changelog highlights (v0.44.0 → v0.45.0)
- Upstream release includes breaking changes for module-specific client adapters (CockroachDB/Dex/examples paths).
- Security-related note: dependency/security upgrades (including OTel log SDK bump) are included.
- No CVE/GHSA specifically tied to APIs used by this repository’s current
testcontainers-gousage was identified in the release body.
Usage in this repository
testing/e2e/agent_container_test.goimports and usestestcontainerscontainer lifecycle APIs.testing/e2e/stand_alone_container_test.gousestestcontainers.GenericContainerand container endpoint/health checks.testing/e2e/scaffold/scaffold.gousestestcontainers-go/modules/toxiproxy.
Compatibility assessment
- The reported upstream breaking changes target modules not used here (CockroachDB/Dex client adapters).
- Current usage is container orchestration + toxiproxy test scaffolding, which remains compatible.
- Impact is limited to test/e2e paths under
testing/(no production runtime dependency surface).
github.com/Shopify/toxiproxy/v2 v2.12.0 → v2.13.0
Ecosystem: Go
| Check | Result |
|---|---|
| Breaking changes | ✅ None found for this repo usage |
| Testable in PR | ✅ Yes (Buildkite PR pipeline covers e2e test paths using toxiproxy) |
Changelog highlights (v2.12.0 → v2.13.0)
- Added optional bearer-token auth for Toxiproxy HTTP API (
TOXIPROXY_AUTH_TOKEN) and warning on unauthenticated non-loopback API. - Fixed hangs/panics in toxic handling (
remove toxic, bandwidth toxic rate edge cases, slicer toxic validation). - No CVE/GHSA IDs listed in the module changelog section for 2.13.0.
Usage in this repository
testing/e2e/stand_alone_container_test.goandtesting/e2e/stand_alone_test.gousetoxiproxy/clientto create/remove toxics and validate Fleet Server degradation/recovery behavior.
Compatibility assessment
- Repository usage (creating/removing toxics, proxy lookups) is unchanged by the noted updates.
- New auth option is additive; existing unauthenticated local/integration usage remains valid.
- Fixes reduce flake/hang risk in failure-injection tests.
Go toolchain directive in testing/go.mod 1.26.10 → 1.27.0
Ecosystem: Go
| Check | Result |
|---|---|
| Breaking changes | ✅ None found in current CI mode; requires Go 1.27 toolchain for testing/ module |
| Testable in PR | ✅ Yes |
Changelog highlights (1.26.10 → 1.27.0)
- This is a Go toolchain requirement bump for the nested
testingmodule (not an application runtime library bump).
Usage in this repository
magee2e paths executego testwithcmd.Dir = "testing"(magefile.go), so this directive applies to test execution.
Compatibility assessment
- With
GOTOOLCHAIN=auto,goresolves and runs successfully fortesting/. - Operational impact is limited to contributor/CI environments that force
GOTOOLCHAIN=localand stay on Go 1.26.x.
Labels Applied
oblt-aw/ai/merge-ready— risk low-to-moderate, no repo-used breaking API/input changes identified, and impact is confined to test tooling.
What is this? | From workflow: Observability Agentic Workflow — Pull Request
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
Automerge skippedAutomerge skipped this pull request because the To allow automerge for this kind of update, enable the matching collection under Automerge on the Control Plane Dashboard (the See Opt in or opt out for how to enable or disable Automerge collections on the Control Plane Dashboard. Collections currently enabled for automerge: Changed files considered:
|
TL;DRBuildkite failed in Remediation
Investigation detailsRoot Cause
After showing that diff, CI reports:
Given this PR updates test-tooling dependencies ( Evidence
Verification
Follow-up
What is this? | From workflow: Observability Agentic Workflow — Status Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. |
This PR contains the following updates:
v2.12.0→v2.13.0v0.44.0→v0.45.0v0.44.0→v0.45.0Release Notes
testcontainers/testcontainers-go (github.com/testcontainers/testcontainers-go)
v0.45.0Compare Source
What's Changed
🔒 Security
🚀 Features
🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
📦 Dependency updates
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate CLI.