Skip to content
This repository has been archived by the owner on May 22, 2024. It is now read-only.

Support SpecFlow v4 #92

Merged
merged 2 commits into from
Dec 14, 2022
Merged

Support SpecFlow v4 #92

merged 2 commits into from
Dec 14, 2022

Conversation

mbhoek
Copy link
Member

@mbhoek mbhoek commented Dec 2, 2022

Initial work to support SpecFlow v4.

  • support .NET Framework v4.6.2 (and above)
  • support .NET v6.0.0 (and above)
  • upgrade dependencies to latest

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.

Requires .NET Framework v4.6.2 or above.
Requires .NET 6.0.0 or above.

+semver: major
@mbhoek mbhoek added the enhancement New feature or request label Dec 2, 2022
@mbhoek mbhoek added this to the Support SpecFlow v4 milestone Dec 2, 2022
@mbhoek mbhoek self-assigned this Dec 2, 2022
@mbhoek mbhoek merged commit 5550e7f into main Dec 14, 2022
@mbhoek mbhoek deleted the feature/specflow4 branch December 14, 2022 16:13
@mbhoek
Copy link
Member Author

mbhoek commented Dec 16, 2022

I've rolled back this PR by force pushing the v3.9.3 tagged commit of main. That was also not a good idea.

The reason for rolling back is that work for v4 was already in main, so for example the README.md would already say that this plugin supports v4 and up -- which is true for the sources but I did not release the package to NuGet yet so this might cause confusion. Future me, please only complete PRs that you intend to release a packages soon.

@mbhoek mbhoek removed this from the Support SpecFlow v4 milestone Dec 16, 2022
@solidtoken solidtoken locked as resolved and limited conversation to collaborators Dec 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Development

Successfully merging this pull request may close these issues.

1 participant