Release 6.0.0

[djbe]

I've moved the "bug fixes" changelog section to be after "new features". I've adapted the rake script as well. The order is now:

• Breaking changes
• New features
• Bug fixes
• Internal changes

[AliSoftware]

I'll do a PR to link to the new wiki page about swiftlint custom rules before we merge this PR

[AliSoftware]

(We should also include #508 in this release)

[AliSoftware]

Might be the best occasion to update our internal release process doc in our wiki (which is supposed to serve as a guide to ourselves, really): https://github.com/SwiftGen/SwiftGen/wiki/%5BAdmin%5D-Release-Process

[djbe]

I've updated the Update the version of SwiftGen section in that wiki page. I'm not familiar enough with the release process to update the Publish a new release accordingly.

[djbe]

@AliSoftware right, so I wrongly assumed that the CLI template name option was called --templateName when I updated the error messages and docs (it's called --template).

We can either leave them as is, or add new options that match those docs and deprecate the old one (see last commit 05e0b88). Not sure if that warrants a mention in the MG, as the old option is still around.

[AliSoftware]

Wait seriously? It was still --template the whole time?
I say we rename it to match the config file and mark the old one as deprecated

[AliSoftware]

So iiuc basically what you did in the last commit, right?

[djbe]

Jep.

[djbe]

Question is: changelog entry and MG entry? Or skip 'em?

[AliSoftware]

CHANGELOG entry I think yes, we need to trace that somewhere at least. MG entry probably not worth it, the overall suggestion in the MG already being basically "Y U Not use a config file already?" anyway 😜

[AliSoftware]

TODO: Update the playground + rakelib/playground.rake since we recently renamed the YAML resources