Release a new version

[bmorelli25]

Running into the following error when trying to use binary:

❯ ./docs-builder serve -p ../docs-builder/docs/source
:: fail: Program[0] System.Exception: /Users/brandon/Documents/GitHub/tools is not a git repository.    at Elastic.Markdown.IO.GitConfiguration.Create(IFileSystem) + 0x3b0    at Elastic.Markdown.BuildContext..ctor(IFileSystem, IFileSystem, String, String) + 0x198    at Documentation.Builder.Http.DocumentationWebHost..ctor(String, ILoggerFactory, IFileSystem) + 0x94    at Documentation.Builder.Cli.Commands.<Serve>d__3.MoveNext() + 0xa4 --- End of stack trace from previous location ---    at ConsoleAppFramework.ConsoleApp.ConsoleAppBuilder.<RunCommand0Async>d__24.MoveNext() + 0x1bc

This was fixed in #144. There are a lot of other fixes we should get into a new release before giving this to writers.

[Mpdreamz]

Just released 0.2.0

https://github.com/elastic/docs-builder/releases/tag/0.2.0

Releasing is as easy as creating a release on github with the right version number.

Once @reakaleek's proposed automation lands a draft release will be ready with the correct release notes and version number based on the changes that are going in. Making it even easier.

In my opinion any one in @elastic/docs-engineering should be able to release minors and patches at any time. Release often! :)

[reakaleek]

#202

[bmorelli25]

Fantastic!

[Mpdreamz]

Closing this as we decided everyone on the team is allowed to release minors and patches at any time.