Skip to content
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.

Investigate using sematic-release #334

Closed
JDawes-ScottLogic opened this issue Aug 8, 2017 · 3 comments
Closed

Investigate using sematic-release #334

JDawes-ScottLogic opened this issue Aug 8, 2017 · 3 comments

Comments

@JDawes-ScottLogic
Copy link
Collaborator

Investigate using semantic-release for the release process.

@JDawes-ScottLogic
Copy link
Collaborator Author

semantic-release probably won't work as we're using lerna, but it looks like there's a compatible fork: https://github.com/atlassian/lerna-semantic-release

@ColinEberhardt
Copy link
Collaborator

If it makes it simpler, I don't think it's a big issue if all of our lerna packages are versioning with the same number. My gut feeling is that this would be simpler from a semver perspective.

Anyhow, feels like a low priority over features / examples / testing at the moment, as long as releases have an easy to follow documented process

@JDawes-ScottLogic
Copy link
Collaborator Author

Duplicate of #232

@JDawes-ScottLogic JDawes-ScottLogic marked this as a duplicate of #232 Aug 10, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants