Release v4.7.8

[jaylinski]

It is time...

for a new release.

This PR prepares a new patch-release and updates release-instructions.

Note: the release system will be kept as is for the 4.x-branch but will be updated for 5.x.

Closes #1918.

Commit diff

v4.7.7...4.x

npm publish diff

npm diff [email protected] [email protected]

Comparison with previous release

a9a8e40

[nknapp]

I have quickly scanned through the changes since the last release. Good work on that and thank you for your support. I have a few questions/remarks though. Nothing that is blocking the release...

• Was there a problem with prettier formatting markdown files? c295ef0#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519L124

• In arturmakaranka@86a9615#diff-08181b000accdc767af533084f693abdb80df0683dbfff3e6f64b1facc92d6daR1266 I think if would be helpful if the parameter i had a better name.

As for the release: It has been a long while since I have published one. But if I recall correctly, I never used a release-branch. Is there any reason why the newer commits on the 4.x branch shouldn't be part of the release?

[jaylinski]

@nknapp Thanks for the review.

• Regarding the markdown formatting with prettier: this was only done in lint-staged-husky command, put not in npm run format. That's why I removed it. I re-added it in this PR: Format *.md files with prettier #1976
• True, do you have a suggestion? I'm not sure, since i for iteration seems already not that bad 😅

Regarding the release branch: it already contains all commits from 4.x. But I only added non-chore commits to the release-notes.