Bump marocchino/sticky-pull-request-comment from 2.5.0 to 2.7.0

[dependabot]

Bumps marocchino/sticky-pull-request-comment from 2.5.0 to 2.7.0.

Release notes

Sourced from marocchino/sticky-pull-request-comment's releases.

v2.6.2

Reverted changes in version 2.6. As a result, the base_url has been removed.

v2.6.1

Change base_url default to ${{ env.GITHUB_API_URL }}

v2.6.0

• Update deps
• Add base_url option. (default: 'https://api.github.com')

Commits

• f6a2580 📦️ build
• 3a69964 Merge pull request #1036 from aburgel/main
• f7a1435 Merge pull request #1037 from marocchino/dependabot/npm_and_yarn/octokit/grap...
• 39859c4 build(deps): Bump @​octokit/graphql-schema from 14.22.0 to 14.23.0
• dd4c8a0 Merge branch 'marocchino:main' into main
• 99a69fc Merge pull request #1034 from marocchino/dependabot/npm_and_yarn/eslint-plugi...
• df32075 build(deps-dev): Bump eslint-plugin-github from 4.9.0 to 4.9.2
• 8139bff Merge pull request #1033 from marocchino/dependabot/npm_and_yarn/typescript-e...
• e647f68 build(deps-dev): Bump @​typescript-eslint/parser from 6.0.0 to 6.1.0
• f21f977 📦️ build
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

The following labels could not be found: dependencies-github-actions.

[pr-commenter]

Bloop Bleep... Dogbot Here

Regression Detector Results

Run ID: d2362f3d-8dee-48e9-b916-3f57991f9413
Baseline: dff2b98
Comparison: 5150a61
Total datadog-agent CPUs: 7

Explanation

A regression test is an integrated performance test for datadog-agent in a repeatable rig, with varying configuration for datadog-agent. What follows is a statistical summary of a brief datadog-agent run for each configuration across SHAs given above. The goal of these tests are to determine quickly if datadog-agent performance is changed and to what degree by a pull request.

Because a target's optimization goal performance in each experiment will vary somewhat each time it is run, we can only estimate mean differences in optimization goal relative to the baseline target. We express these differences as a percentage change relative to the baseline target, denoted "Δ mean %". These estimates are made to a precision that balances accuracy and cost control. We represent this precision as a 90.00% confidence interval denoted "Δ mean % CI": there is a 90.00% chance that the true value of "Δ mean %" is in that interval.

We decide whether a change in performance is a "regression" -- a change worth investigating further -- if both of the following two criteria are true:

1. The estimated |Δ mean %| ≥ 5.00%. This criterion intends to answer the question "Does the estimated change in mean optimization goal performance have a meaningful impact on your customers?". We assume that when |Δ mean %| < 5.00%, the impact on your customers is not meaningful. We also assume that a performance change in optimization goal is worth investigating whether it is an increase or decrease, so long as the magnitude of the change is sufficiently large.

2. Zero is not in the 90.00% confidence interval "Δ mean % CI" about "Δ mean %". This statement is equivalent to saying that there is at least a 90.00% chance that the mean difference in optimization goal is not zero. This criterion intends to answer the question, "Is there a statistically significant difference in mean optimization goal performance?". It also means there is no more than a 10.00% chance this criterion reports a statistically significant difference when the true difference in mean optimization goal is zero -- a "false positive". We assume you are willing to accept a 10.00% chance of inaccurately detecting a change in performance when no true difference exists.

The table below, if present, lists those experiments that have experienced a statistically significant change in mean optimization goal performance between baseline and comparison SHAs with 90.00% confidence OR have been detected as newly erratic. Negative values of "Δ mean %" mean that baseline is faster, whereas positive values of "Δ mean %" mean that comparison is faster. Results that do not exhibit more than a ±5.00% change in their mean optimization goal are discarded. An experiment is erratic if its coefficient of variation is greater than 0.1. The abbreviated table will be omitted if no interesting change is observed.

No interesting changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%.

Fine details of change detection per experiment.

experiment	goal	Δ mean %	Δ mean % CI	confidence
uds_dogstatsd_to_api	ingress throughput	+0.23	[-0.36, +0.83]	38.43%
trace_agent_json	ingress throughput	+0.03	[+0.00, +0.05]	88.87%
otel_to_otel_logs	ingress throughput	+0.00	[-0.06, +0.07]	7.41%
tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.06, +0.06]	2.46%
file_to_blackhole	egress throughput	-0.00	[-1.45, +1.44]	0.31%
trace_agent_msgpack	ingress throughput	-0.08	[-0.11, -0.05]	99.94%
tcp_syslog_to_blackhole	ingress throughput	-0.52	[-0.57, -0.47]	100.00%

[duncanpharvey]

Handled in #22590

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.