Skip to content

Remove dependabot for instrumentations#8504

Merged
bouwkast merged 5 commits intomasterfrom
steven/remove-dependabot-for-instrumentations
Apr 23, 2026
Merged

Remove dependabot for instrumentations#8504
bouwkast merged 5 commits intomasterfrom
steven/remove-dependabot-for-instrumentations

Conversation

@bouwkast
Copy link
Copy Markdown
Collaborator

Summary of changes

This removes the dependabot configuration and related code/projects for updating instrumentations.

Reason for change

Dependabot would trigger and then open a PR like so Bump log4net from 3.3.0 to 3.3.1.

Then our workflow would trigger and raise this PR [Test Package Versions Bump] Updating package versions

Ultimately we don't really act on these dependabot PRs so they don't add a ton of value.

To compensate for the potential loss in visibility I've opted to add a single additional run on Wednesday which will regenerate the [Test Package Versions Bump] if still open from Sunday's.

Depending on how this goes we may want to remove the Wednesday additional run, but running it on Wednesday will mean that any cooldown packages skipped on Sunday will get bumped which may be helpful.

Implementation details

  • Removed all the dependabot honeypot projects - I don't think we need them anymore they were used by dependabot to do the bumping
  • Removed all code that updated/touched those projects
  • Removed the dependabot config for the integrations
  • Updated/Removed the github workflow that opens the [Test Package Versions Bump] to no longer look for the dependabot PRs (will need to close them manually) and to run on Wednesday too.

Test coverage

none

Other details

@pr-commenter
Copy link
Copy Markdown

pr-commenter Bot commented Apr 22, 2026

Benchmarks

Benchmark execution time: 2026-04-23 15:01:25

Comparing candidate commit 209e3b5 in PR branch steven/remove-dependabot-for-instrumentations with baseline commit 33380a2 in branch master.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 27 metrics, 0 unstable metrics, 58 known flaky benchmarks, 29 flaky benchmarks without significant changes.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

Known flaky benchmarks

These benchmarks are marked as flaky and will not trigger a failure. Modify FLAKY_BENCHMARKS_REGEX to control which benchmarks are marked as flaky.

scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net6.0

  • 🟩 throughput [+9684.376op/s; +11935.132op/s] or [+8.140%; +10.032%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • 🟥 execution_time [+306.796ms; +310.049ms] or [+152.243%; +153.857%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net6.0

  • 🟥 execution_time [+383.518ms; +385.989ms] or [+303.002%; +304.955%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces netcoreapp3.1

  • 🟥 execution_time [+396.080ms; +398.576ms] or [+350.516%; +352.725%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody net472

  • 🟥 allocated_mem [+1.308KB; +1.308KB] or [+27.529%; +27.541%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody net6.0

  • 🟥 allocated_mem [+471 bytes; +472 bytes] or [+9.977%; +9.987%]
  • 🟩 execution_time [-15.296ms; -11.123ms] or [-7.144%; -5.195%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody netcoreapp3.1

  • 🟥 allocated_mem [+1.272KB; +1.272KB] or [+27.502%; +27.510%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody net472

  • 🟥 allocated_mem [+1.307KB; +1.307KB] or [+105.746%; +105.759%]
  • 🟥 throughput [-254032.240op/s; -249123.353op/s] or [-25.938%; -25.437%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody net6.0

  • 🟥 allocated_mem [+471 bytes; +472 bytes] or [+38.558%; +38.566%]
  • 🟩 execution_time [-26.273ms; -21.424ms] or [-11.717%; -9.554%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody netcoreapp3.1

  • 🟥 allocated_mem [+1.272KB; +1.272KB] or [+105.292%; +105.304%]
  • 🟥 throughput [-140945.262op/s; -125036.594op/s] or [-20.251%; -17.965%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody net6.0

  • 🟩 throughput [+9161.735op/s; +12130.147op/s] or [+5.829%; +7.718%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody netcoreapp3.1

  • 🟩 throughput [+7185.061op/s; +9822.026op/s] or [+5.724%; +7.825%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody net6.0

  • 🟩 throughput [+433996.872op/s; +454390.394op/s] or [+14.471%; +15.151%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody netcoreapp3.1

  • 🟩 execution_time [-18.587ms; -14.164ms] or [-8.568%; -6.529%]
  • 🟩 throughput [+156626.699op/s; +214823.175op/s] or [+6.217%; +8.527%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs net472

  • 🟥 execution_time [+300.090ms; +300.744ms] or [+149.945%; +150.272%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs net6.0

  • 🟥 execution_time [+300.497ms; +303.636ms] or [+151.542%; +153.124%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs netcoreapp3.1

  • 🟥 execution_time [+299.158ms; +301.558ms] or [+150.692%; +151.901%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs net472

  • 🟥 execution_time [+297.461ms; +298.225ms] or [+146.101%; +146.476%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs net6.0

  • 🟥 execution_time [+295.984ms; +298.795ms] or [+144.696%; +146.070%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs netcoreapp3.1

  • 🟥 execution_time [+301.297ms; +302.814ms] or [+150.588%; +151.346%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack net6.0

  • 🟥 execution_time [+24.328µs; +48.076µs] or [+7.767%; +15.348%]
  • 🟥 throughput [-444.376op/s; -244.966op/s] or [-13.852%; -7.636%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net472

  • 🟥 execution_time [+299.625ms; +300.344ms] or [+149.544%; +149.902%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net6.0

  • unstable execution_time [+302.844ms; +354.230ms] or [+329.052%; +384.886%]
  • 🟩 throughput [+1110.072op/s; +1255.254op/s] or [+9.122%; +10.315%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest netcoreapp3.1

  • unstable execution_time [+298.605ms; +336.027ms] or [+226.728%; +255.142%]
  • 🟩 throughput [+652.768op/s; +852.128op/s] or [+6.319%; +8.249%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • unstable execution_time [+372.907ms; +468.899ms] or [+171.459%; +215.595%]
  • 🟥 throughput [-589.464op/s; -523.176op/s] or [-53.411%; -47.405%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net6.0

  • unstable execution_time [+202.475ms; +335.721ms] or [+86.286%; +143.070%]
  • 🟥 throughput [-743.758op/s; -660.320op/s] or [-49.609%; -44.044%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces netcoreapp3.1

  • 🟥 execution_time [+338.133ms; +346.086ms] or [+202.243%; +207.000%]
  • 🟥 throughput [-406.753op/s; -371.519op/s] or [-28.322%; -25.868%]

scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice net6.0

  • 🟩 execution_time [-155.871µs; -121.006µs] or [-7.896%; -6.130%]
  • 🟩 throughput [+34.670op/s; +44.001op/s] or [+6.844%; +8.686%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net472

  • 🟥 execution_time [+302.381ms; +303.572ms] or [+152.273%; +152.873%]
  • 🟩 throughput [+18484.706op/s; +20087.020op/s] or [+5.948%; +6.464%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net6.0

  • 🟥 execution_time [+300.826ms; +303.119ms] or [+150.745%; +151.893%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch netcoreapp3.1

  • 🟥 execution_time [+301.898ms; +305.319ms] or [+151.661%; +153.379%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net472

  • 🟥 execution_time [+300.582ms; +301.701ms] or [+150.942%; +151.504%]
  • 🟩 throughput [+15626.036op/s; +17083.411op/s] or [+5.235%; +5.723%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net6.0

  • 🟥 execution_time [+299.098ms; +301.602ms] or [+147.891%; +149.129%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync netcoreapp3.1

  • 🟥 execution_time [+303.533ms; +307.026ms] or [+153.844%; +155.614%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net472

  • 🟥 execution_time [+301.010ms; +302.471ms] or [+151.080%; +151.813%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net6.0

  • 🟥 execution_time [+299.882ms; +302.047ms] or [+149.464%; +150.543%]
  • 🟩 throughput [+39427.356op/s; +44396.972op/s] or [+7.829%; +8.816%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync netcoreapp3.1

  • 🟥 execution_time [+300.369ms; +303.274ms] or [+149.431%; +150.876%]

scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog net6.0

  • 🟩 execution_time [-16.060ms; -12.375ms] or [-7.468%; -5.754%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark net6.0

  • 🟩 allocated_mem [-18.734KB; -18.714KB] or [-6.834%; -6.826%]
  • unstable execution_time [-59.662µs; -7.463µs] or [-11.792%; -1.475%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark net6.0

  • 🟥 execution_time [+7.051µs; +10.818µs] or [+16.666%; +25.570%]
  • 🟥 throughput [-4982.683op/s; -3260.490op/s] or [-20.976%; -13.726%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark netcoreapp3.1

  • unstable execution_time [-14.717µs; -7.613µs] or [-22.833%; -11.811%]
  • 🟩 throughput [+1995.638op/s; +3489.449op/s] or [+12.244%; +21.409%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net472

  • 🟥 execution_time [+301.125ms; +303.311ms] or [+152.205%; +153.310%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net6.0

  • 🟥 execution_time [+303.479ms; +305.874ms] or [+154.470%; +155.689%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog netcoreapp3.1

  • 🟥 execution_time [+299.612ms; +301.679ms] or [+149.993%; +151.027%]

scenario:Benchmarks.Trace.RedisBenchmark.SendReceive net6.0

  • 🟩 throughput [+35565.446op/s; +46614.660op/s] or [+6.732%; +8.823%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net472

  • 🟥 execution_time [+299.533ms; +301.198ms] or [+149.290%; +150.120%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net6.0

  • 🟥 execution_time [+301.302ms; +302.500ms] or [+151.299%; +151.901%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog netcoreapp3.1

  • 🟥 execution_time [+302.201ms; +304.350ms] or [+153.257%; +154.347%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net472

  • 🟥 execution_time [+299.610ms; +300.365ms] or [+149.447%; +149.824%]
  • 🟩 throughput [+66109106.555op/s; +66381171.191op/s] or [+48.145%; +48.343%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net6.0

  • 🟥 execution_time [+418.584ms; +421.882ms] or [+520.584%; +524.686%]
  • 🟩 throughput [+982.799op/s; +1160.825op/s] or [+7.598%; +8.974%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore netcoreapp3.1

  • 🟥 execution_time [+299.463ms; +300.415ms] or [+149.365%; +149.840%]
  • 🟩 throughput [+18240894.942op/s; +19183851.707op/s] or [+8.080%; +8.497%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net6.0

  • 🟩 throughput [+101225.157op/s; +108309.073op/s] or [+9.451%; +10.112%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope netcoreapp3.1

  • 🟩 throughput [+47211.175op/s; +66786.086op/s] or [+5.465%; +7.730%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net6.0

  • 🟩 throughput [+97725.281op/s; +127339.081op/s] or [+7.564%; +9.856%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan netcoreapp3.1

  • 🟩 throughput [+91533.010op/s; +99398.904op/s] or [+9.091%; +9.872%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes net6.0

  • 🟩 throughput [+51890.360op/s; +56698.634op/s] or [+9.422%; +10.295%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes netcoreapp3.1

  • 🟩 throughput [+27614.165op/s; +37144.838op/s] or [+6.181%; +8.314%]

scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net6.0

  • 🟩 throughput [+79771.615op/s; +104623.719op/s] or [+8.912%; +11.689%]

Known flaky benchmarks without significant changes:

  • scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net472
  • scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild netcoreapp3.1
  • scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody net472
  • scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody net472
  • scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark net472
  • scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark net6.0
  • scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark netcoreapp3.1
  • scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack net472
  • scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack netcoreapp3.1
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net472
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net6.0
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice netcoreapp3.1
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool net472
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool net6.0
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool netcoreapp3.1
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice net472
  • scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice netcoreapp3.1
  • scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog net472
  • scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog netcoreapp3.1
  • scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark net472
  • scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark netcoreapp3.1
  • scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark net472
  • scenario:Benchmarks.Trace.RedisBenchmark.SendReceive net472
  • scenario:Benchmarks.Trace.RedisBenchmark.SendReceive netcoreapp3.1
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net472
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net472
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes net472
  • scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net472
  • scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin netcoreapp3.1

@bouwkast bouwkast marked this pull request as ready for review April 22, 2026 19:34
@bouwkast bouwkast requested review from a team as code owners April 22, 2026 19:34
@bouwkast bouwkast added the area:dependabot dependabot updates label Apr 22, 2026
Copy link
Copy Markdown
Member

@andrewlock andrewlock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

Comment thread .github/workflows/auto_bump_test_package_versions.yml Outdated
Co-authored-by: Andrew Lock <andrew.lock@datadoghq.com>
@bouwkast bouwkast merged commit 8c6215f into master Apr 23, 2026
136 of 139 checks passed
@bouwkast bouwkast deleted the steven/remove-dependabot-for-instrumentations branch April 23, 2026 18:43
@github-actions github-actions Bot added this to the vNext-v3 milestone Apr 23, 2026
andrewlock added a commit that referenced this pull request Apr 29, 2026
## Summary of changes

Lists the package versions that were updated in the description of
version-bump PRs

## Reason for change

In #8504 we removed all the "honeypot" csproj files that dependabot was
using, mostly because the PRs it was creating weren't very useful, were
noisy, and required us to trigger a separate PR anyway, so we switched
to a schedule.

However, when reviewing the [[Test Package Versions Bump]
PRs](#8502), these files
were the main ones I was reviewing, as they were easy to read. As a
workaround, this PR extends the "cool down report" to be a more
generalized "bump report", that lists the changes to the packages that
_were_ bumped too.

We could extend this even further in the future to include release note
changes (like dependabot does) or `dotnet inspect` updates, as we've
discussed in the past, though I can also see those being overly noisy
for the common cases.

## Implementation details

Extend the existing report to include the list of packages that _were_
bumped too.

## Test coverage

Ran it locally, and it produced the following: 

## Package Version Updates

Bold entries indicate **major**-version bumps. `(new)` means no previous
version existed.

| Package | Integration | Previous | New | Published |
|---------|-------------|----------|-----|-----------|
| AWSSDK.Core | AwsSdk | 4.0.3.30 | 4.0.3.31 | 2026-04-20 |
| MongoDB.Driver | MongoDB | 3.7.1 | 3.8.0 | 2026-04-20 |
| HotChocolate.AspNetCore | HotChocolate | 15.1.14 | 15.1.15 |
2026-04-22 |
| MySql.Data | MySqlData | 9.6.0 | 9.7.0 | 2026-04-22 |
| Microsoft.Data.Sqlite | MicrosoftDataSqlite | 10.0.6 | 10.0.7 |
2026-04-21 |
| log4net | log4net | 3.3.0 | 3.3.1 | 2026-04-19 |
| OpenTelemetry.Api | OpenTelemetry | 1.15.2 | 1.15.3 | 2026-04-21 |

## Package Version Cooldown Report

The following versions were published less than **2 days** ago and have
been overridden.
These require manual review before inclusion.

| Package | Integration | Overridden Version | Published | Age (days) |
|---------|-------------|--------------------|-----------|------------|
| AWSSDK.Core | AwsSdk | 3.7.500.96 | 2026-04-23 | 0 |
| AWSSDK.Core | AwsSdk | 4.0.3.32 | 2026-04-22 | 1 |
| AWSSDK.DynamoDBv2 | AwsDynamoDb | 3.7.513.2 | 2026-04-23 | 0 |
| AWSSDK.DynamoDBv2 | AwsDynamoDb | 4.0.17.10 | 2026-04-22 | 1 |
| AWSSDK.Kinesis | AwsKinesis | 3.7.506.19 | 2026-04-23 | 0 |
| AWSSDK.Kinesis | AwsKinesis | 4.0.8.12 | 2026-04-22 | 1 |
| AWSSDK.SQS | AwsSqs | 3.7.502.55 | 2026-04-23 | 0 |
| AWSSDK.SQS | AwsSqs | 4.0.2.26 | 2026-04-22 | 1 |
| AWSSDK.SimpleNotificationService | AwsSns | 3.7.502.59 | 2026-04-23 |
0 |
| AWSSDK.SimpleNotificationService | AwsSns | 4.0.2.28 | 2026-04-22 | 1
|
| AWSSDK.EventBridge | AwsEventBridge | 3.7.502.60 | 2026-04-23 | 0 |
| AWSSDK.EventBridge | AwsEventBridge | 4.0.5.27 | 2026-04-22 | 1 |
| AWSSDK.S3 | AwsS3 | 3.7.511.6 | 2026-04-23 | 0 |
| AWSSDK.S3 | AwsS3 | 4.0.22 | 2026-04-22 | 1 |
| AWSSDK.StepFunctions | AwsStepFunctions | 3.7.502.48 | 2026-04-23 | 0
|
| AWSSDK.StepFunctions | AwsStepFunctions | 4.0.2.21 | 2026-04-22 | 1 |
chojomok added a commit that referenced this pull request Apr 30, 2026
Per @bouwkast: PR #8504 (Remove dependabot for instrumentations) removed
the dependabot scaffolding for instrumentation integrations. This file
was authored before that change landed and is no longer wanted on master.

Re-running GeneratePackageVersions confirmed no MassTransit-specific
regen output — the new MT entries that this PR added were already
correct, so no generated-file changes are needed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
chojomok added a commit that referenced this pull request Apr 30, 2026
Brings in the round-1/2/3 cleanup pass from mt7 (constant + tag
removals, the ContextPropagation file split, baggage merge for
extracted contexts, reflection caching, etc.) plus the master merge.

Conflict resolution:
- tracer/dependabot/integrations/Datadog.Dependabot.MassTransit.csproj
  was deleted on mt7 per #8504 (Steven Bouwkamp's removal of the
  dependabot scaffolding for instrumentation integrations). MT8 had a
  modified version bumping the package to 8.5.8 — kept the deletion
  since #8504 covers MT8 too.
- mt7 commit 987206c ("Remove MT8-only and dead methods from
  MassTransitCommon") removed GetActivityKind, SetActivityKind,
  CreateResourceName, and EnhanceActivityMetadata as dead code on
  mt7. They are *not* dead on mt8 — MassTransitActivityHandler
  references SetActivityKind and EnhanceActivityMetadata. Restored
  the four methods on the mt8 side of the merge.

BuildTracerHome green across all TFMs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dependabot dependabot updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants