Keeping a permalink changelog in the main branch makes it easier for nuget package users to discover what's changing across versions.
A new workflow should be created that triggers on release.published that updates the global changelog so that it includes the newly created release.
If that release, for whatever reason, ends up not being published to nuget and is instead entirely deleted, a subsequent one would fixup the changelog anyway, so there's no harm in updating it on release publishing, rather than "released" (which only happens for non-prerelease).
Keeping a permalink changelog in the main branch makes it easier for nuget package users to discover what's changing across versions.
A new workflow should be created that triggers on release.published that updates the global changelog so that it includes the newly created release.
If that release, for whatever reason, ends up not being published to nuget and is instead entirely deleted, a subsequent one would fixup the changelog anyway, so there's no harm in updating it on release publishing, rather than "released" (which only happens for non-prerelease).