Adjust versions, bounds and CHANGELOGs to account for the latest release

[lehins]

Description

Recent release requires some adjustments on master.

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated
• When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
  versioning process.
• The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
• All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
• Code is formatted with fourmolu (use scripts/fourmolize.sh)
• Cabal files are formatted (use scripts/cabal-format.sh)
• hie.yaml has been updated (use scripts/gen-hie.sh)
• Self-reviewed the diff

[aniketd]

If I understand correctly, we bump version numbers on master after every release, so that ongoing development can easily add changelog under the next bump, or bump it further, whichever is necessary?

[lehins]

If I understand correctly, we bump version numbers on master after every release, so that ongoing development can easily add changelog under the next bump, or bump it further, whichever is necessary?

@aniketd Yes, this is the step 4 in the release process

[aniketd]

LGTM! 🙌

[teodanciu]

Looks good to me