Update module github.com/alessio/shellescape to v1.6.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/alessio/shellescape	v1.4.2 → v1.6.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

alessio/shellescape (github.com/alessio/shellescape)

v1.6.0

Compare Source

What's Changed

• Fix ExampleQuoteCommand by @​alexandear in #​31
• README: fix typo by @​alexandear in #​30
• github actions by @​ccoVeille in #​32
• golangci lint by @​ccoVeille in #​33
• Bump golangci/golangci-lint-action from 6.1.0 to 6.2.0 by @​dependabot in #​36
• Bump actions/dependency-review-action from 4.4.0 to 4.5.0 by @​dependabot in #​35
• Bump codecov/codecov-action from 4.6.0 to 5.3.1 by @​dependabot in #​34
• Bump golangci/golangci-lint-action from 6.2.0 to 6.5.0 by @​dependabot in #​38
• Update codacy.yml by @​alessio in #​39
• Update build.yaml by @​alessio in #​40
• Update golangci-lint.yml by @​alessio in #​41
• Update dependency-review.yml by @​alessio in #​42
• Update CODE_OF_CONDUCT.md by @​alessio in #​44
• Update README.md by @​alessio in #​45
• Refresh Go toolchain by @​alessio in #​46
• shellescape: new ScanTokens function by @​alessio in #​47
• add CODECOV_TOKEN by @​alessio in #​48

New Contributors

• @​alexandear made their first contribution in #​31
• @​ccoVeille made their first contribution in #​32
• @​dependabot made their first contribution in #​36

Full Changelog: alessio/shellescape@v1.5.1...v1.6.0

v1.5.1

Compare Source

Changelog

• Fixes for #​28
  • aaff7ce update readme to use the new vanity name
  • eee5f61 update playground example's URL

v1.5.0

Compare Source

Changelog

• 312088d Create sonarqube.yml
• 823e979 add testable example (#​24)
• 27a48e3 fail fast on errors
• bb4dcb3 fix imports
• 4f9bf6b fix imports (#​26)
• 1b4bdc1 new testable example
• a6eeed4 remove sonarqube config file
• a5719a4 update build config
• 6d0d828 update gitignore
• a792e00 update gitignore, add Makefile
• 62618b3 update go.mod and go.sum

---

Configuration

📅 Schedule: (in timezone Europe/Paris)

• Branch creation
  • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
  • Only on Sunday and Saturday (* * * * 0,6)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: test/e2e-framework/go.sum

Command failed: go get -t ./...
go: github.com/alessio/shellescape@v1.6.0: parsing go.mod:
	module declares its path as: al.essio.dev/pkg/shellescape
	        but was required as: github.com/alessio/shellescape

[dd-prapprover]

PRApprover will approve and merge this PR, FAQ, #dx-source-code-management

🛠️ PRApproval Status

• ✅ PR is eligible for auto-approval by rule datadog-agent-renovate - 2026-06-21T11:17:35Z
• ⬜ CI tests passed
• ⬜ Approved
• Manual merge required: this rule does not auto-merge.

➡️ Current phase: CI tests failed. Please fix the failing tests to continue.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 192e66cf7a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Require shellescape by its new module path

The v1.6.0 tag no longer declares itself as github.com/alessio/shellescape; its go.mod module path is al.essio.dev/pkg/shellescape, while the framework still imports the old path in test/e2e-framework/components/command/unixOSCommand.go:15. With this requirement, any command resolving the e2e-framework module will fail on a module-path mismatch before tests or builds can run; either keep v1.4.2 or update the requirement and imports to the new module path.

Useful? React with 👍 / 👎.

[datadog-prod-us1-6]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 51.09% (+0.12%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 50b1fcb | Docs | Datadog PR Page | Give us feedback!}

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor a19f5789:

Results for datadog-agent_7.82.0~devel.git.275.50b1fcb.pipeline.120500476-1_amd64.deb:

No change detected

[dd-octo-sts]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor a19f578
📊 Static Quality Gates Dashboard
🔗 SQG Job

33 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	748.825 MiB
✅	agent_deb_amd64_fips	704.783 MiB
✅	agent_heroku_amd64	308.644 MiB
✅	agent_msi	616.860 MiB
✅	agent_rpm_amd64	748.809 MiB
✅	agent_rpm_amd64_fips	704.767 MiB
✅	agent_rpm_arm64	724.372 MiB
✅	agent_rpm_arm64_fips	683.925 MiB
✅	agent_suse_amd64	748.809 MiB
✅	agent_suse_amd64_fips	704.767 MiB
✅	agent_suse_arm64	724.372 MiB
✅	agent_suse_arm64_fips	683.925 MiB
✅	docker_agent_amd64	807.652 MiB
✅	docker_agent_arm64	808.223 MiB
✅	docker_agent_jmx_amd64	998.549 MiB
✅	docker_agent_jmx_arm64	987.773 MiB
✅	docker_cluster_agent_amd64	208.060 MiB
✅	docker_cluster_agent_arm64	221.314 MiB
✅	docker_cws_instrumentation_amd64	7.447 MiB
✅	docker_cws_instrumentation_arm64	6.877 MiB
✅	docker_dogstatsd_amd64	39.004 MiB
✅	docker_dogstatsd_arm64	37.117 MiB
✅	docker_host_profiler_amd64	305.020 MiB
✅	docker_host_profiler_arm64	316.111 MiB
✅	dogstatsd_deb_amd64	29.743 MiB
✅	dogstatsd_deb_arm64	27.798 MiB
✅	dogstatsd_rpm_amd64	29.743 MiB
✅	dogstatsd_suse_amd64	29.743 MiB
✅	iot_agent_deb_amd64	45.671 MiB
✅	iot_agent_deb_arm64	42.390 MiB
✅	iot_agent_deb_armhf	43.175 MiB
✅	iot_agent_rpm_amd64	45.672 MiB
✅	iot_agent_suse_amd64	45.671 MiB

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: d109a645-8d6f-49cb-87d3-c576a3f2bce8

Baseline: f5ae1d8
Comparison: 1812c25
Diff

❌ Experiments with retried target crashes

This is a critical error. One or more replicates failed with a non-zero exit code. These replicates may have been retried. See Replicate Execution Details for more information.

• quality_gate_idle

Optimization Goals: ❌ Regression(s) detected

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
❌	quality_gate_logs	% cpu utilization	+5.07	[+3.94, +6.20]	1	Logs bounds checks dashboard

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
❌	quality_gate_logs	% cpu utilization	+5.07	[+3.94, +6.20]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	+0.02	[-0.03, +0.07]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	-0.20	[-0.24, -0.16]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	-0.29	[-0.35, -0.23]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.32	[-0.36, -0.29]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	-0.39	[-0.64, -0.14]	1	Logs bounds checks dashboard
➖	quality_gate_security_no_fs_load	memory utilization	-0.44	[-0.53, -0.35]	1	Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	quality_gate_idle	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	145.99MiB ≤ 154MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	576.02KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	482.28MiB ≤ 495MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	0.89MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	183.34MiB ≤ 195MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	264.17MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	329.87 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	396.43MiB ≤ 430MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	total_bytes_received	10/10	0.86GiB ≤ 1.04GiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	36.64 ≤ 40	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	297.99MiB ≤ 330MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	60.47 ≤ 80	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	273.83MiB ≤ 310MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	30.25 ≤ 40	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	277.01MiB ≤ 320MiB	bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

Replicate Execution Details

We run multiple replicates for each experiment/variant. However, we allow replicates to be automatically retried if there are any failures, up to 8 times, at which point the replicate is marked dead and we are unable to run analysis for the entire experiment. We call each of these attempts at running replicates a replicate execution. This section lists all replicate executions that failed due to the target crashing or being oom killed.

Note: In the below tables we bucket failures by experiment, variant, and failure type. For each of these buckets we list out the replicate indexes that failed with an annotation signifying how many times said replicate failed with the given failure mode. In the below example the baseline variant of the experiment named experiment_with_failures had two replicates that failed by oom kills. Replicate 0, which failed 8 executions, and replicate 1 which failed 6 executions, all with the same failure mode.

Experiment	Variant	Replicates	Failure	Logs	Debug Dashboard
experiment_with_failures	baseline	0 (x8) 1 (x6)	Oom killed		Debug Dashboard

The debug dashboard links will take you to a debugging dashboard specifically designed to investigate replicate execution failures.

❌ Retried Normal Replicate Execution Failures (non-profiling)

Experiment	Variant	Replicates	Failure	Debug Dashboard
quality_gate_idle	comparison	7	Oom killed	Debug Dashboard

❌ Retried Profiling Replicate Execution Failures (ddprof)

Note: Profiling replicas may still be executing. See the debug dashboard for up to date status.

Experiment	Variant	Replicates	Failure	Debug Dashboard
quality_gate_idle	comparison	10	Oom killed	Debug Dashboard
quality_gate_idle_all_features	baseline	10	Oom killed	Debug Dashboard
quality_gate_idle_all_features	comparison	10	Oom killed	Debug Dashboard
quality_gate_logs	baseline	10	Oom killed	Debug Dashboard
quality_gate_logs	comparison	10	Oom killed	Debug Dashboard
quality_gate_metrics_logs	baseline	10	Oom killed	Debug Dashboard
quality_gate_metrics_logs	comparison	10	Oom killed	Debug Dashboard
quality_gate_security_idle	baseline	10	Oom killed	Debug Dashboard

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_security_no_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-24 09:35:56 UTC ℹ️ Start processing command /merge

---

2026-06-24 09:36:07 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-06-24 09:37:13 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 2h (p90).

---

2026-06-24 10:25:05 UTC ℹ️ MergeQueue: This merge request was merged