This repository has been archived by the owner on May 22, 2024. It is now read-only.
Support SpecFlow v4 #97
Merged
Conversation
This file contains 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
|
This is the same work as in #92 but since I reverted that PR this is a new submission. |
Requires .NET Framework v4.6.2 or above. Requires .NET 6.0.0 or above. +semver: major
mbhoek
force-pushed
the
feature/specflow4
branch
from
d94979f
to
92c3888
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Initial work to support SpecFlow v4.
Note: this drops support for frameworks which are no longer maintained by Microsoft, i.e. .NET Framework v4.6.1, .NET Core v3.1 and .NET v5.0. See .NET Framework Lifecycle Policy and .NET and .NET Core Lifecycle Policy.