Skip to content

chore(deps): update dependency fsharp.core to v11#5128

Merged
thomhurst merged 1 commit intomainfrom
renovate/fsharp.core-11.x
Mar 10, 2026
Merged

chore(deps): update dependency fsharp.core to v11#5128
thomhurst merged 1 commit intomainfrom
renovate/fsharp.core-11.x

Conversation

@thomhurst
Copy link
Owner

This PR contains the following updates:

Package Type Update Change
FSharp.Core (source) nuget major 10.0.10411.0.100

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@thomhurst thomhurst added dependencies Pull requests that update a dependency file MAJOR renovate-bot labels Mar 10, 2026
@thomhurst thomhurst enabled auto-merge (squash) March 10, 2026 21:16
Copy link
Contributor

@claude claude bot left a comment

Choose a reason for hiding this comment

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

Code Review: FSharp.Core major version bump (10.0.104 → 11.0.100)

This is a Renovate-generated dependency update with a single-line change in Directory.Packages.props.

Summary

The change itself is minimal and correct — a straightforward version pin update. However, since this is a major version bump, a few things are worth noting:

Points to Verify

FsCheck Compatibility
The repo pins FsCheck at 3.3.2 alongside this FSharp.Core update. FsCheck has historically had tight FSharp.Core version constraints. Worth confirming that FsCheck 3.3.2 declares FSharp.Core >= 11.0.100 as a supported range (NuGet will resolve it, but a mismatch in the declared dependency range can cause warnings or unexpected behavior at runtime).

Downstream F# projects
Several projects consume this version centrally:

  • TUnit.Assertions.FSharp
  • TUnit.FsCheck
  • TUnit.TestProject.FSharp
  • Templates

FSharp.Core 11.x is released with .NET SDK 11.0, and while the NuGet package itself is multi-targeting friendly, CI confirmation that all F# project builds and tests pass is the key gate here — all checks are still pending at the time of this review.

Assessment

The change is appropriate and follows the project's pattern of keeping dependencies current. Once the pending CI (particularly modularpipeline and integration-tests) passes and confirms no regressions in the F#/FsCheck test projects, this should be safe to merge.

No structural concerns with the change itself. ✓

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file MAJOR renovate-bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants