Bump github.com/invopop/jsonschema from 0.12.0 to 0.13.0

[dependabot]

Bumps github.com/invopop/jsonschema from 0.12.0 to 0.13.0.

Commits

• 328cc73 Merge pull request #159 from misberner/mi/custom-comment-lookup
• 83557f4 Trying to fix running test workflow
• 20dafe1 Add a custom mechanism for looking up comments.
• 42b1bb0 Merge pull request #158 from invopop/codecov
• fd4a187 Testing support for full comments
• 26cd70a Fixing linter issues
• c404ce3 Updating actions
• cb1a2f6 Codecov. Minor renaming of comments handler
• a446707 Merge pull request #111 from cloudquery/fix/no-format-limits
• 15fa257 Linter bump
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor 5d09f2cebf006fe22de3b4679c530b2f33299e96

Diff per package

package	diff	status	size	ancestor	threshold
datadog-heroku-agent-amd64-deb	0.00MB	✅	505.28MB	505.27MB	70.00MB
datadog-iot-agent-amd64-deb	0.00MB	✅	113.34MB	113.34MB	10.00MB
datadog-iot-agent-x86_64-rpm	0.00MB	✅	113.41MB	113.41MB	10.00MB
datadog-iot-agent-x86_64-suse	0.00MB	✅	113.41MB	113.41MB	10.00MB
datadog-agent-amd64-deb	0.00MB	✅	1190.85MB	1190.85MB	140.00MB
datadog-agent-x86_64-rpm	0.00MB	✅	1200.17MB	1200.17MB	140.00MB
datadog-agent-x86_64-suse	0.00MB	✅	1200.17MB	1200.17MB	140.00MB
datadog-agent-arm64-deb	0.00MB	✅	935.11MB	935.11MB	140.00MB
datadog-agent-aarch64-rpm	0.00MB	✅	944.41MB	944.41MB	140.00MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	78.54MB	78.54MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	78.62MB	78.62MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	78.62MB	78.62MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	55.75MB	55.75MB	10.00MB
datadog-iot-agent-arm64-deb	0.00MB	✅	108.81MB	108.81MB	10.00MB
datadog-iot-agent-aarch64-rpm	-0.00MB	✅	108.88MB	108.88MB	10.00MB

Decision

✅ Passed

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 99f4c019-8c4c-4939-bf57-b9d94f9b6331

Baseline: 5d09f2c
Comparison: 33e34a0
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+1.89	[-1.35, +5.13]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.90	[+0.82, +0.99]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	+0.78	[+0.70, +0.86]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.41	[-0.05, +0.88]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.11	[-0.57, +0.79]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.10	[-0.68, +0.88]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.06	[-0.81, +0.92]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.05	[-0.83, +0.92]	1	Logs
➖	quality_gate_idle	memory utilization	+0.03	[-0.00, +0.07]	1	Logs bounds checks dashboard
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.02	[-0.80, +0.85]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.01	[-0.76, +0.78]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.01, +0.02]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.11, +0.11]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.01	[-0.70, +0.69]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.02	[-0.67, +0.62]	1	Logs
➖	file_tree	memory utilization	-0.87	[-1.00, -0.74]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http1	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http1	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http2	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http2	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency_linear_load	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	lost_bytes	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_300ms_latency	lost_bytes	10/10
✅	file_to_blackhole_300ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10
✅	quality_gate_logs	memory_usage	10/10

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

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.