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.
Version number and documentation updates for 4.1.0.
I've added the file changes.rst. I think it is important to keep track of, and document, user-visible changes, and I think this document should be kept up to date as new changes are committed, not just when assembling a final release.
So my first thought was to ask people to update this file every time they make a pull request. But that would create merge conflicts (& even if the person merging the pull can resolve those conflicts, github can't do so itself and therefore this would break workflow checks.) And I don't want to start encouraging people to merge or cherry-pick changes from the main branch into their feature branch (rebasing would be fine, but for some reason a lot of people seem to be allergic to rebasing.) So... I don't have a good solution here, and would welcome suggestions. :)