-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IdentityModel assemblies have incorrect assembly version #3565
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Except it's not that simple. This script is authored in PowerShell. We can't be making use of non-source-built tools like this as part of the built logic. So really the only option is to reimplement the PowerShell script in Bash. The other issue is that the script's logic uses |
@mthalman - should this issue remain open until the version test baseline has been updated to reflect the fix that went into IdentityModel is picked up? |
Sure, that's fine |
Builds are all passing now and assembly version comparisons are all good. |
When comparing assembly versions between the Microsoft SDK and the source-built SDK, the following diff showed up:
These assemblies are produced from source-build-externals. The package version is being set correctly. However, the source of the external repo is configured in such a way to default the assembly version to 0.0.1 and it must be explicitly overriden. The repo does contain a script to overwrite this file which makes use of the settings in a config file that contains the correct version. So it should just be a matter of customizing the source-build-externals build to invoke this script. This script is also called by the repo's own release pipeline.
The text was updated successfully, but these errors were encountered: