Scalar.AspNetCore changelog no longer documents bundled frontend dependency updates

What happens?

I'm using:

<PackageReference Include="Scalar.AspNetCore" Version="2.16.16" />

and recently noticed a change in authentication behavior related to multiple security requirements, apparently introduced by #8888.

Previously, when multiple authentication schemes were selected, Scalar applied all of them to the request. Now, even with Multiple selected, only the scheme from the currently active authentication tab is sent.

I understand this was likely changed to be more compliant with the OpenAPI specification, where separate security requirement objects represent OR, but this behavior used to work differently.

The problem is that it's difficult to determine which frontend/API Reference version is bundled with a given Scalar.AspNetCore release.

Recent changelog entries such as:

2.16.16 2.16.15 2.16.14

contain no dependency information, while older releases included sections like:

Updated Dependencies

• @scalar/[email protected]

What did you expect to happen?

I expected behavioral changes in the bundled frontend to be traceable from the Scalar.AspNetCore changelog.

Please include bundled frontend dependency versions in the changelog, or provide another documented way to determine which frontend version is included in each Scalar.AspNetCore release.

This would make changes like #8888 much easier to diagnose from the .NET consumer side.

OpenAPI Document

No response