Criteria or timeline for a stable (non-prerelease) Microsoft.ApplicationInsights.NLogTarget 3.x

Two questions, both cheap to answer:

1. What are the criteria or timeline for promoting the LOGGING packages — specifically Microsoft.ApplicationInsights.NLogTarget — from -beta1 to stable?
2. If there is no plan to do that, what is the recommended supported path for NLog users before the 2.x retirement on 03/31/2027?

Is your feature request related to a problem?

On the 3.x base SDK there is no non-prerelease NLog option. The latest stable Microsoft.ApplicationInsights.NLogTarget is 2.23.0 (2025-02-19); the latest overall is 3.1.2-beta1 (2026-05-28). Readme.md states "Beta packages are not recommended for use in production & support is limited." Learn says the .NET Application Insights Classic API SDK 2.x "is deprecated and retires on 03/31/2027", and the migration guidance lists "Microsoft.ApplicationInsights.NLogTarget for NLog integration (beta)" as the 3.x package.

Describe the solution you'd like.

Publish NLogTarget on the stable track alongside the next main-package release.

NLogTarget 3.1.2-beta1 and stable Microsoft.ApplicationInsights 3.1.2 were built from the same commit (552c52030df5, per the <repository> element in both nuspecs), and the beta already depends on the stable Microsoft.ApplicationInsights 3.1.2 on both net462 and net8.0. As far as I can tell the only prerelease thing about it is the version suffix: deleting the <PropertyGroup Label="LOGGING Version Override"> from LOGGING/Directory.Build.targets would let LOGGING inherit the empty PreReleaseMilestone from .props/_GlobalStaticVersion.props. That file's own comment reads "To promote LOGGING to the same version as main packages, remove this PropertyGroup."

Describe alternatives you've considered.

Unlike Microsoft.Extensions.Logging.ApplicationInsights in #3170, there is no 3.x replacement to fall back to. MigrationGuidance.md lists every other logging adapter as unsupported but keeps a #### NlogTarget section, so "remove the dependency and use your ILoggers as-is" does not apply here.

Additional context.

Flagging the known 3.x deltas so they are not a surprise: the TFMs move from net452/netstandard2.0 to net462/net8.0, and InstrumentationKey is replaced by ConnectionString/Credential. I am asking about the release track only — not asking for API or TFM changes. Happy to open the PR if removing that override is the whole change. If promoting it is not planned, that is equally useful to know and we will budget a move to the Azure Monitor OpenTelemetry Distro instead.

Start with LOGGING/Directory.Build.targets and .props/_GlobalStaticVersion.props, then compare the package metadata described in the issue. Check the NLogTarget project and its release configuration against the stable main package. Done means the promotion criteria or timeline is documented, or the release-track change is validated and the supported alternative is stated.