Prep for v4

[luketomlinson]

Changes

• Create dist for changes
• Create changelog

[luketomlinson]

@C0ZEN FYI ☝️

[luketomlinson]

@C0ZEN The standard-version tool didn't work as well as I'd hoped. You have to be pretty strict about following the commit convention and we haven't been. So this changelog is manual

[C0ZEN]

@luketomlinson at least on my side I think my PR titles are good but yeah, every tool is about having a strict syntax.
If you want to enforce it, there are actions that could simply check the PR titles and mark as fail the check if not OK.

[C0ZEN]

@luketomlinson is it WIP?

[flaxel]

@C0ZEN The standard-version tool didn't work as well as I'd hoped. You have to be pretty strict about following the commit convention and we haven't been. So this changelog is manual

Oh that's probably because of my commits. I didn't find any comments on the commit messages, which is why I didn't pay attention. Would it make sense to write a comment in the contributing file how to name the pull requests?

[C0ZEN]

@flaxel dunno.
The right place for this would be the contributing file, but in fact we just don't care about people commits.
Only the PR title matters and for this, I really think a bot like https://github.com/zeke/semantic-pull-requests would be perfect.

[flaxel]

An action such as action-semantic-pull-request could also be used if it is not intended to be an app.

[flaxel]

@luketomlinson When do you think you can release the new version?

[luketomlinson]

@flaxel @C0ZEN I wanted to see if we should get #508 in since it is a breaking change.

[C0ZEN]

@luketomlinson I don't think so because actually, I still didn't find the way to implement it.

[C0ZEN]

@luketomlinson dunno if you are waiting an approval, so I made a final review and voilà ;)

[C0ZEN]

Suggested change

	## [4.0.0](https://github.com/actions/stale/compare/v3.0.19...v4.0.0) (2021-06-18)
	## [4.0.0](https://github.com/actions/stale/compare/v3.0.19...v4.0.0) (2021-06-27)

[C0ZEN]

@luketomlinson any news?