Skip to content

deps(archive): bump AppInsights 2.23.0→3.1.0 + restore OTel pin (redux)#44

Merged
jppaquet merged 1 commit into
mainfrom
deps/archive-appinsights-3.1.0-otel-pin-redux
May 6, 2026
Merged

deps(archive): bump AppInsights 2.23.0→3.1.0 + restore OTel pin (redux)#44
jppaquet merged 1 commit into
mainfrom
deps/archive-appinsights-3.1.0-otel-pin-redux

Conversation

@jppaquet
Copy link
Copy Markdown
Owner

@jppaquet jppaquet commented May 6, 2026

Summary

PR #33 landed this on 2026-05-05 evening, but PR #30 (azure-sdks) was branched from main before #33 and reverted `Notify.Archive.csproj` back to AppInsights 2.23.0 when it merged. Dependabot's #42 then tried again and failed CI on the same OTel vuln.

Manual landing — same fix as #33:

  • `Microsoft.ApplicationInsights.WorkerService` 2.23.0 → 3.1.0
  • Pin `OpenTelemetry.Api` 1.15.3 (3.1.0 pulls 1.15.1 transitively, GHSA-g94r-2vxg-569j)

Closes #42.

Test plan

  • `dotnet build src/Notify.Archive/Notify.Archive.csproj -c Release -warnaserror` clean.
  • CI green on this PR.

Follow-up worth considering

A `Directory.Packages.props` or central NuGet pin would prevent this from happening a third time. Three projects now reference AppInsights/OTel pins individually; central management would let the next Dependabot bump preserve them automatically.

PR #33 originally landed this on 2026-05-05 evening, but PR #30 (azure-sdks)
was branched from main BEFORE #33 merged and reverted Notify.Archive.csproj
back to AppInsights 2.23.0 when it landed. Dependabot's PR #42 then tried
to bump again and failed CI on the same OTel transitive vuln.

Manual landing again. Closes #42. Same fix:
- Microsoft.ApplicationInsights.WorkerService 2.23.0 → 3.1.0
- Pin OpenTelemetry.Api 1.15.3 (3.1.0 pulls 1.15.1 transitively, GHSA-g94r-2vxg-569j)

Notify.IngestionApi already has the same pin from PR #21.
@jppaquet jppaquet merged commit 02504b6 into main May 6, 2026
10 of 11 checks passed
@jppaquet jppaquet deleted the deps/archive-appinsights-3.1.0-otel-pin-redux branch May 6, 2026 23:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant