Release 3.13 #3703
Merged
Release 3.13 #3703
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
Annotate attributes
Typo in readme fix
Adding data dictionary should not add a trailing newline
…d ParameterizedFixtureSuite when building test fixtures
Fix mixed line endings in Git
.NET Core 2.2 and 3.0 are no longer supported and we should test 3.1
…ValuePairConstraint.cs Co-Authored-By: Mikkel Nylander Bundgaard <mikkelbu@users.noreply.github.com>
…eConstraintTests.cs Co-Authored-By: Mikkel Nylander Bundgaard <mikkelbu@users.noreply.github.com>
…ValuePairConstraint.cs Co-Authored-By: Mikkel Nylander Bundgaard <mikkelbu@users.noreply.github.com>
…Constraint.cs Co-Authored-By: Mikkel Nylander Bundgaard <mikkelbu@users.noreply.github.com>
* Add default values to FormatCollection method parameters * Better failure messages for Subset and Superset constraints * Add ExtraItems comment * Replace FormatCollection usages to use default values.
fix: Make CI work again
…ash-issue-3563
…ash-issue-3662
Initial implementation for looking for property defined in interface
….com/wbratz/nunit into wbratz-wbratz/Depreciate-Debug-writer-class
Issue 2211 - Add support of indexers to the PropertyConstraint
…ter-class Merge latest from master
Merge latest from master
Merge latest from master
…lass Adds obsolete comment to debug writer class issue #2680
Improve TextMessageWriter output for numeric values
RepeatAttribute increments CurrentRepeatCount on each repeat iteration
Add test verifying equality works for Complex on all platforms
IStructuralEquatable support
Closed
|
This is ready for review. I'd like to merge and release from the merge build tomorrow Jan 7 if possible because I put that date in the |
mikkelbu
approved these changes
Jan 7, 2021
There was a problem hiding this comment.
I'm a bit unsure how to review this, but from your comment I've taken a look at changes.md and also checked some files (~ 30-40 where the changes looked as I would have expected). Perhaps tonight (5 hours) I can check it in some more detail.
EDIT: I just took a look at the diff between the master and this PR - git diff master..release313 - and I think it looks sound.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates the copyright year to 2021 and merges all changes from master into the release branch.
This tests a new release process where I will test the NuGet packages built in Azure DevOps to verify the release, then once this PR is merged, allow Azure DevOps to build the code and I will release the artifacts created by that build. I no longer want to build and release from developer machines.
For future releases, I'd like to automate the release whenever changes are merged to the release branch.
I'm setting this to draft for now. I need to finish updating
Changes.mdand testing the new process.Once this is complete, I will submit a PR to the docs repo with the changes to the process.