Limit OpenFeature fixture submodule updates

[leoromanovsky]

Motivation

PR #11355 added Dependabot updates for git submodules so the OpenFeature fixture corpus can stay current. Because the rule was scoped to the repository root without an allow-list, Dependabot also started opening JMX Fetch submodule updates, such as #11863. Those updates should remain owned by the existing JMX/APM Java flow, while OpenFeature fixture updates should be labeled and routed to the FFE SDK team.

Changes

This PR restricts the gitsubmodule Dependabot rule to dd-smoke-tests/openfeature/src/test/resources/ffe-system-test-data using an explicit allow entry.

It also applies the expected labels to generated OpenFeature fixture submodule PRs:

• comp: openfeature
• tag: dependencies
• tag: no release notes

Decisions

I kept directory: / because Dependabot reads git submodules from the repository .gitmodules file. The narrower allow rule is the guardrail that prevents the same automation from updating dd-java-agent/agent-jmxfetch/integrations-core.

The follow-up request also asked about CODEOWNERS assignment. I checked that path before changing it: the existing /dd-smoke-tests/openfeature/ CODEOWNERS rule already covers dd-smoke-tests/openfeature/src/test/resources/ffe-system-test-data, including the submodule gitlink path that changes in fixture update PRs. Adding an exact duplicate owner line would not change routing, so this PR intentionally leaves CODEOWNERS unchanged.

Validation

• ruby -e "require 'yaml'; YAML.load_file('.github/dependabot.yml'); puts 'dependabot.yml OK'"
• git config -f .gitmodules --get-regexp '^submodule\\..*\\.path$'
• git diff --check

[datadog-prod-us1-3]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 56.92% (-0.01%)

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

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.76 s	14.68 s	[-0.2%; +1.3%] (no difference)
startup:insecure-bank:tracing:Agent	13.70 s	13.71 s	[-0.9%; +0.8%] (no difference)
startup:petclinic:appsec:Agent	16.90 s	16.60 s	[+0.7%; +2.9%] (maybe worse)
startup:petclinic:iast:Agent	16.26 s	16.94 s	[-8.3%; +0.3%] (no difference)
startup:petclinic:profiling:Agent	16.70 s	16.91 s	[-2.3%; -0.2%] (maybe better)
startup:petclinic:sca:Agent	16.94 s	16.65 s	[+0.8%; +2.7%] (maybe worse)
startup:petclinic:tracing:Agent	16.02 s	15.92 s	[-0.4%; +1.6%] (no difference)

Commit: 24e949cd · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[PerfectSlayer]

Thanks for the follow up commit!

[leoromanovsky]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-07 15:29:05 UTC ℹ️ Start processing command /merge

---

2026-07-07 15:29:15 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-07-07 16:23:13 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-07-07 18:23:44 UTC ❌ MergeQueue: The build pipeline has timeout

The merge request has been interrupted because the build 8972795207992346701 took longer than expected. The current limit for the base branch 'master' is 120 minutes.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-07 16:22:43 UTC ℹ️ Start processing command /merge

---

2026-07-07 16:22:45 UTC ❌ MergeQueue

PR already in the queue with status waiting

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-07 18:33:56 UTC ℹ️ Start processing command /merge

---

2026-07-07 18:34:00 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-07-07 19:39:45 UTC ℹ️ MergeQueue: This merge request was merged