This is a long-running PR that starts the implementation of a release process in parts, in order to remove the manual release and to start fixing the issues described in #57.

• Automate the linking to the documentation of the latest release tag in the README.md
• Replace the version number in the header of the src/js.cookie.js file without using variables to keep the number in the original file
• Implement grunt-release(or similar) to remove most part of the manual work
• Automatically upload the minified file into the github release (grunt-release does not support it)
• Automate the commit with the message "Prepare for the next development iteration"
• Automate the release on npm
• Review the README release docs
• Test manually each release command one by one
• Run tests before release, should stop if there are failures
• Comment the npm publish ./ command and test the whole release manually

Update March 20, 2016:

I have considered creating a task-agnostic decoupled node module for releases that is easily testable.

Making Grunt tasks testable will require so many effort that it turns out creating a new module will be much more efficient.

Also, considering the amount of requirements from #57, it makes no sense coupling everything to a lot of Grunt Tasks. We need to have better maleability to be able to implement custom routines for the release process.

Update March 29, 2016:

Repository is public, still in development: https://github.com/js-cookie/js-cookie-release