chore: fix TUnit.Assertions.FSharp pre-release package version#4926
Merged
chore: fix TUnit.Assertions.FSharp pre-release package version#4926
Conversation
thomhurst
temporarily deployed
to
Pull Requests
GitHub Actions
Inactive
thomhurst
temporarily deployed
to
Pull Requests
GitHub Actions
Inactive
thomhurst
temporarily deployed
to
Pull Requests
GitHub Actions
Inactive
thomhurst
force-pushed
the
fix/fsharp-prerelease
branch
from
1c736ca to
1d18d57
Compare
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
Contributor
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. This is a clean, correct fix that aligns |
thomhurst
force-pushed
the
fix/fsharp-prerelease
branch
from
1d18d57 to
ef6f71e
Compare
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
Update TUnit.Assertions.FSharp version from 0.75.38-PullRequest3485.0 to 1.16.4 to match all other TUnit packages in Directory.Packages.props.
thomhurst
force-pushed
the
fix/fsharp-prerelease
branch
from
ef6f71e to
0c034a5
Compare
thomhurst
temporarily deployed
to
Pull Requests
GitHub Actions
Inactive
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
temporarily deployed
to
Pull Requests
GitHub Actions
Inactive
This was referenced Feb 22, 2026
Open
This was referenced Feb 23, 2026
Open
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
TUnit.Assertions.FSharpversion inDirectory.Packages.propsfrom0.75.38-PullRequest3485.0(a stale pre-release version from PR Improve AOT annotations + Various fixes #3485) to1.16.4to match all other TUnit packages.Context
The
TUnit.Assertions.FSharpentry inDirectory.Packages.propswas set to0.75.38-PullRequest3485.0, which is a pre-release version from an old pull request build. All other TUnit packages (TUnit,TUnit.Core,TUnit.Engine,TUnit.Assertions,TUnit.AspNetCore) are at version1.16.4. This inconsistency could cause issues for F# projects that consume TUnit via NuGet, sinceTUnit.Assertions.propsautomatically adds a PackageReference toTUnit.Assertions.FSharpfor.fsprojfiles.Closes #4884
Test plan
dotnet build TUnit.Assertions.FSharp/TUnit.Assertions.FSharp.fsprojsucceeds