Add versionist config

[brownjohnf]

Change-Type: patch

[brownjohnf]

I'm confused because this repo seems to already be versioned, but I don't see any versionbot integration.

[Page-]

Is a versionist.conf.js needed? What differences do we want from the default?

Also this is versioned manually currently, it's from long before versionist existed

[brownjohnf]

You have to use a versionist config any time there's no package.json in the repo.

[hedss]

This also needs the CHANGELOG.md file to be updated to use the standard header:

# Change Log

All notable changes to this project will be documented in this file
automatically by Versionist. DO NOT EDIT THIS FILE MANUALLY!
This project adheres to [Semantic Versioning](http://semver.org/).

[hedss]

There's actually now a better way of doing this, removing this line and just adding the option:

  editVersion: false,

[brownjohnf]

Done

[lurch]

...except this particular config doesn't update NPM package info ;-)

[brownjohnf]

Fixed

[lurch]

Any reason for using this here, when the 'upstream' versionist.conf.js does:

const execSync = require('child_process').execSync;

const getAuthor = (commitHash) => {
  return execSync(`git show --quiet --format="%an" ${commitHash}`, {
    encoding: 'utf8'
  }).replace('\n', '');
};

IMHO if any differences can be minimised, that'd be ideal.
At the moment, I'm aware of resin-base, edge-node-manager and leech all using their own versionist.conf.js files. See also product-os/versionist#84

[brownjohnf]

Nope. I've just been copy/pasting this file around from repo to repo for a while now.

[lurch]

Ah, so I guess you were probably copy'n'pasting round an old version of a variant of versionist's versionist.conf.js, and the 'upstream version' of versionist.conf.js has since been updated. And I guess this will continue to be a problem for any resin.io projects that are using versionist / VersionBot but aren't using NPM, so I wonder if product-os/versionist#84 needs to be expanded into a more flexible long-term solution...?

[lurch]

Is a versionist.conf.js needed? What differences do we want from the default?

See my suggestion in product-os/versionist#84 (comment)

[lurch]

This also needs the CHANGELOG.md file to be updated to use the standard header

Given that we're mandating the same standards across all resin.io repos, is that something else that versionist or VersionBot could check?

[hedss]

@lurch You know where the issues list is... :)

[lurch]

product-os/versionist#90

[ghost]

VersionBot failed to commit a new version to prepare a merge for the above pull request here: #33. The reason for this is:
Cannot read property 'split' of undefined
Please carry out relevant changes or alert an appropriate admin.

[brownjohnf]

@hedss this is a weird error:

VersionBot failed to commit a new version to prepare a merge for the above pull request here: #33. The reason for this is:
Cannot read property 'split' of undefined
Please carry out relevant changes or alert an appropriate admin.

[hedss]

@brownjohnf I think I know what this is, the versioning doesn't have v prefixes. I'm going to create a new tag with this version and hopefully it should work.

[hedss]

@brownjohnf Yep, twas the tag. Merged, all good.