Release process minor

tl;dr

This is a quick summary of the steps we go through to validate a minor before publishing

1. Update dependencies

First we try bumping all our dependencies and peer dependencies to the latest minor* available and run npm audit afterwards, to make sure our dependencies/peer dependencies include security risks.

* we don't bump any major version of dependencies between minor releases, so you dont have to. we'll try to bundle major update of dependencies to major releases. thats why the next major is scheduled for may/june (after angular 8)

2. Local validation

First we use the differnet sandboxes we use to develop new features. the sandboxes are available here. If no breaking changes or bugs are found we go to

3. Publish release candidate

once the code has been validated locally, a 2.x.0-rc.0 is published through npm. you can access it either through specific version targetting or through npm tag next

$ npm i @lucca-front/[email protected]
$ npm i @lucca-front/scss@next

4. Integration to a third party website

Then we use this release candidate and try to upgrade an application already using lucca-front. we usually go for tproj or poplee review.

If a bug or a breaking change is found, we go through steps 1, 2, 3 all over again.

5. Official release

If the release candidate is successfully used in either tporj our talent whithout a itch, then the official release follows under the tag latest

6. Update documentation

then, the documentation available here is updated to reflect the new features and evolution of the library