Version increment/deploy path

[DeviaVir]

Thinking about, and open for suggestions, a release management that can automatically increment and tag latest version on changes to master.

Needs to update:

• CHANGELOG.md
• test/main.js#L65
• package.json version

Travis? Git hooks?

[abetomo]

I think it would be better to use Travis CI.
Would you like me to create a release script?

[abetomo]

@DeviaVir What can I do to help?

[DeviaVir]

@abetomo I would like to see how a release script (travis) would look like, any samples you know of?

[abetomo]

@DeviaVir I will try to create samples by 6/2 !

[abetomo]

@DeviaVir
I am not confident of what you expected, but I created a sample.

1. Add the setting .travis.yml.

   • If you put the following settings, it will be released automatically when tag is pushed.
   • sample: https://github.com/abetomo/node-ss2json/blob/master/.travis.yml
   • reference: https://docs.travis-ci.com/user/deployment/npm

2. Release script created in sample

   • I intended to be able to do something similar to requests automatically.
   • sample: https://github.com/abetomo/node-ss2json/blob/master/release-script.sh

(The sample script project is a simple one made just to confirm the operation.
It is not exactly the same as node-lambda, but I think that it is okay with almost the same processing.)

[DeviaVir]

@abetomo step 1:
#304
can you review?

[DeviaVir]

still considering step 2, it would be great if travis could take over the entire process of tagging, bumping version and pusing that all to master..

[abetomo]

@DeviaVir
PR approved.
As you say, it is best to do all with travis.
I will try to see if it is possible.

[abetomo]

I am checking release processing on travis.
Wait a few more days.

[DeviaVir]

Sure, no rush. Happy with a solution either way.

[abetomo]

@DeviaVir
There are two ways to push from the travis to the repository.

• Use token of github
• Use deploy key

In the case of token, it affects the whole user who created token, but in the case of deploy key, it affects only the registered repository.
Since the impact range is small, we adopted a method using deploy key.

I made a sample up to pushing to master with travis.

1. Use travis-scripts

   • Install and setup according to the document.
   • % npm install @alrra/travis-scripts --save-dev
   • doc: https://github.com/alrra/travis-scripts

2. Updating travis.yml & release-script.sh

   • sample: https://github.com/abetomo/node-ss2json/blob/master/.travis.yml

   - stage: Preparation of npm
   node_js: "7"
   script: "./release-script.sh"
   

   Compared to the file in node-lambda now, the above three lines have been added.

   • sample: https://github.com/abetomo/node-ss2json/blob/master/release-script.sh

3. How to release

   • Pushing a branch whose branch name begins with release/ will be executed until release.

===
If you write everything here, it will be long, so I will only describe the summary and it will end.
Although it is a brief explanation in release-script.sh(https://github.com/abetomo/node-ss2json/blob/master/release-script.sh), I left a comment.
However, I omitted a detailed explanation.
If you have any questions, please ask a question.

[DeviaVir]

@motdotla looks like I don't have access to set up deploy keys myself, any chance you could follow the steps detailed here (or could you somehow give me access to that part of this repo)?