v0.3.1 release

[int-index]

Description

• [BUG] openBinaryFile: resource exhausted (Too many open files) #311
  • Fix a "resource exhausted" crash on repositories containing a large number of Markdown files.

✓ Release Checklist

• I updated the version number in package.yaml.
• I updated the changelog and moved everything
  under the "Unreleased" section to a new section for this release version.
• (After merging) I edited the auto-release.
  • Change the tag and title using the format vX.Y.Z.
  • Write a summary of all user-facing changes.
  • Deselect the "This is a pre-release" checkbox at the bottom.
• (After merging) I updated xrefcheck-action.
• (After merging) I uploaded the package to hackage.

[serokell-bot]

	6 Warnings
⚠️	In 2a43b71 message lacks issue id: v0.3.1 release. See also [Note].
⚠️	In 2a43b71 subject does not begin with an uppercase letter: v0.3.1 release. See also [Note].
⚠️	Description of 2a43b71 does not follow the template. Try Problem:/Solution: structure. If you really have to, you can add And yes, I don't care about templates to the commit message body. See also [Note].
⚠️	Inappropriate title for PR. Should start from issue ID (e.g. [#123]), [Chore] or [Style] tag. Note: please use [Chore] also for tickets tracked internally on YouTrack.
⚠️	Bad issue ID in branch name. Valid format for issue IDs: #123 or chore.
⚠️	Please, only use letters, digits and dashes in the branch name. Found: [".", "."]

[Note]: Skip this check by adding wip, tmp or [temporary] to the commit subject. Fixup commits (marked with fixup! or squash!) are also exempt from this check.

Generated by 🚫 Danger