If something in this list is irrelevant to your PR, you should still set this
checkmark indicating that you are sure it is dealt with (be that by irrelevance).
[x] I made sure my PR addresses a single concern, or multiple concerns which
are inextricably linked. Otherwise I should open multiple PR's.
[x] If I added/removed/deprecated functions/re-exports,
I checked whether these changes impact the .hlint.yaml rules
and updated them if needed.
Related changes (conditional)
Tests
[x] If I added new functionality, I added tests covering it.
[x] If I fixed a bug, I added a regression test to prevent the bug from
silently reappearing again.
Documentation
I checked whether I should update the docs and did so if necessary:
[x] I added an entry to the changelog (creating the Unreleased section if necessary) if my changes are visible to the users
and
[x] provided a migration guide for breaking changes if possible
Stylistic guide (mandatory)
[x] My commit history is clean (only contains changes relating to my
issue/pull request and no reverted-my-earlier-commit changes) and commit
messages start with identifiers of related issues in square brackets.
Example:[#42] Short commit description
If necessary both of these can be achieved even after the commits have been
made/pushed using rebase and squash.
✓ Release Checklist
[x] I updated the version number in universum.cabal.
[x] I updated the changelog and moved everything
under the "Unreleased" section to a new section for this release version.
[x] If any definitions (functions, type classes, instances, etc) were added,
I added @since haddock annotations.
[ ] (After merging) I created a new entry in the releases page,
with a summary of all user-facing changes.
I made sure a tag was created using the format vX.Y.Z
Description
Routine changes to support newer GHC versions.
Related issues(s)
None
✓ Checklist for your Pull Request
Ideally a PR has all of the checkmarks set.
If something in this list is irrelevant to your PR, you should still set this checkmark indicating that you are sure it is dealt with (be that by irrelevance).
.hlint.yamlrules and updated them if needed.Related changes (conditional)
Tests
Documentation
I checked whether I should update the docs and did so if necessary:
Record your changes
Unreleasedsection if necessary) if my changes are visible to the users andStylistic guide (mandatory)
[x] My commit history is clean (only contains changes relating to my issue/pull request and no reverted-my-earlier-commit changes) and commit messages start with identifiers of related issues in square brackets.
Example:
[#42] Short commit descriptionIf necessary both of these can be achieved even after the commits have been made/pushed using rebase and squash.
✓ Release Checklist
universum.cabal.@sincehaddock annotations.vX.Y.Z