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.

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

Update package, language, core and compiler tool versions #6526

Merged
merged 2 commits into from
Apr 16, 2019

Conversation

KevinRansom
Copy link
Member

@KevinRansom KevinRansom commented Apr 13, 2019

Update package, tool and language version numbers.

FSharp.Core package ==> 4.6.3
Microsoft.FSharp.Compiler ==> 10.4.3

FSharp tools banner ==> 10.4.3

Please note: Samples package references need to reflect already shipped versions.

@KevinRansom KevinRansom requested a review from brettfo April 13, 2019 18:17
Copy link
Contributor

@cartermp cartermp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason to bump the FSharp.Core version? Aside from code cleanup there doesn't appear to be any meaningful differences https://github.com/Microsoft/visualfsharp/commits/master/src/fsharp/FSharp.Core

@@ -13,7 +13,6 @@
</ItemGroup>
<ItemGroup>
<PackageReference Include="FSharp.Core" Version="4.6.2" />
<PackageReference Include="FSharp.Core" Version="4.5.2" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is 4.5.2 being removed here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As you can see there are two package references. Clearly one is redundant.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As for bumping the fsharp.core version 4.6.2 has already shipped, this is in preparation for shipping the next one. Which will likely happen when we ship a new compiler, in Dev 16.1

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

4.5.2 removal makes sense here, but is it necessary (from a build process) to rev 4.6.2 with a new compiler if we're not shipping changes?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cartermp, this is in preparation for shipping the next FSharp.Core package. Whether we ship it on a particular date or note is a decision for then.

@KevinRansom KevinRansom merged commit 0d72794 into dotnet:master Apr 16, 2019
@KevinRansom KevinRansom deleted the updatemasterversionnumbers branch July 2, 2019 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants