Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use .NET Package Validation to check for binary compat against baseline #12368

Open
dsyme opened this issue Nov 10, 2021 · 1 comment
Open

Use .NET Package Validation to check for binary compat against baseline #12368

dsyme opened this issue Nov 10, 2021 · 1 comment
Labels
Engineering Impact-Low (Internal MS Team use only) Describes an issue with limited impact on existing code.
Milestone
Backlog

Comments

@dsyme
Copy link
Contributor

dsyme commented Nov 10, 2021

There is a new .NET package verification tool to help check for binary compat

https://devblogs.microsoft.com/dotnet/package-validation/

You can compare against a baseline package

https://devblogs.microsoft.com/dotnet/package-validation/#validation-against-baseline-package-version

We should consider using this for FSharp.Core and FSharp.Compiler.Service
@dsyme
Copy link
Contributor Author

dsyme commented Nov 10, 2021 •
edited
Loading

@colombod did an experiment in using the tool on .NET Interactive here: dotnet/interactive#1726. It's gloriously simple to use, and immediately found an inadvertent breaking change that had broken the .NET Interactive extension ecosystem here: dotnet/interactive#1719

@dsyme dsyme changed the title Use .NET Compatibility checker tool to cehck for binary compat Use .NET Compatibility checker tool to check for binary compat Nov 10, 2021
@dsyme dsyme changed the title Use .NET Compatibility checker tool to check for binary compat Use .NET Package Validation to check for binary compat against baseline Nov 10, 2021
@KevinRansom KevinRansom added the Impact-Low (Internal MS Team use only) Describes an issue with limited impact on existing code. label Jan 26, 2022
@vzarytovskii vzarytovskii moved this to Not Planned in F# Compiler and Tooling Jun 17, 2022
@vzarytovskii vzarytovskii mentioned this issue Oct 3, 2022
Open
@vzarytovskii vzarytovskii added this to the Backlog milestone Oct 19, 2022
@abelbraaksma abelbraaksma mentioned this issue May 5, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Engineering Impact-Low (Internal MS Team use only) Describes an issue with limited impact on existing code.
Projects
F# Compiler and Tooling
Status: New
Milestone
Backlog
Development

No branches or pull requests
3 participants
@vzarytovskii @KevinRansom @dsyme