Assign area:builds to version bump PRs

[NachoEchevarria]

Summary of changes

This PR assigns the label area:builds to version bump PRs.

Reason for change

During releases, version bump PRs are created and they have no label, which makes the workflow add-labels to fail. It's not a big deal, we can manually add a proper label and rerun the workflow, but it's better if we do that automatically.

Implementation details

Test coverage

Other details

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-02-16 11:37:43

Comparing candidate commit 083646b in PR branch nacho/UpdateLabelerRegex with baseline commit 05bb018 in branch master.

Found 9 performance improvements and 13 performance regressions! Performance is the same for 155 metrics, 15 unstable metrics.

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

• 🟩 execution_time [-81.383ms; -80.943ms] or [-40.120%; -39.903%]

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

• 🟥 execution_time [+86.009ms; +86.077ms] or [+76.211%; +76.271%]

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

• 🟥 execution_time [+28.054ms; +32.750ms] or [+14.011%; +16.357%]

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

• 🟥 execution_time [+13.671ms; +20.129ms] or [+6.952%; +10.236%]

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

• 🟩 execution_time [-20.636ms; -13.647ms] or [-21.437%; -14.177%]

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

• 🟥 throughput [-261.414op/s; -156.052op/s] or [-16.769%; -10.011%]

scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net472

• 🟩 execution_time [-145.938µs; -142.076µs] or [-7.047%; -6.860%]
• 🟩 throughput [+35.610op/s; +36.560op/s] or [+7.375%; +7.572%]

scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice netcoreapp3.1

• 🟥 throughput [-223.813op/s; -172.336op/s] or [-43.108%; -33.193%]

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

• 🟩 throughput [+35588.697op/s; +47312.978op/s] or [+8.691%; +11.554%]

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

• 🟥 execution_time [+14.062ms; +17.665ms] or [+7.339%; +9.220%]

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

• 🟥 throughput [-33424.422op/s; -24193.514op/s] or [-7.774%; -5.627%]

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

• 🟥 execution_time [+11.274ms; +16.695ms] or [+5.712%; +8.458%]

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

• 🟥 throughput [-488.261op/s; -284.416op/s] or [-21.936%; -12.778%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net472

• 🟩 execution_time [-10.954ms; -10.773ms] or [-5.420%; -5.330%]

scenario:Benchmarks.Trace.NLogBenchmark.EnrichedLog net472

• 🟩 throughput [+7852.035op/s; +8512.286op/s] or [+6.098%; +6.610%]

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

• 🟩 execution_time [-83.628ms; -81.347ms] or [-47.710%; -46.409%]

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

• 🟩 throughput [+15351298.236op/s; +16325005.080op/s] or [+6.815%; +7.247%]

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

• 🟥 execution_time [+11.996ms; +17.728ms] or [+6.090%; +9.000%]

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

• 🟥 execution_time [+10.386ms; +13.780ms] or [+5.208%; +6.910%]

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

• 🟥 execution_time [+13.696ms; +14.309ms] or [+6.880%; +7.187%]

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

• 🟥 execution_time [+12.083ms; +17.829ms] or [+6.044%; +8.918%]

[andrewlock]

Thanks!