Update maint/maint-67 to 67.1.0.7 #49
Merged
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
This PR updates the
maint/maint-67branch to67.1.0.7.Ah.. it turns out that I forgot that we were using merge commits in order to avoid the tedium of having to manually cherry-pick each single commit over to the maint branch. (For example, see PR #34).
However, I've already cherry-picked over some of the changes in to the maint branch, and while that does work, I could have just made a merge commit.
I've created this PR as a merge commit even though I already cherry-picked over changes in order to keep the history.
However, we can't go back and rewrite the commit history on a public repo, so this PR shows/appears as though it is making the same changes over again as was previously seen in other PRs.
But once this is merged then both branches should have the same original commits.
Note: Once this is merged, I plan on creating a new GitHub release, and then pushing out a new Nuget package.
PR Checklist