Release v0.8.1

fix: fix license header

The license header in all files had wrong date and url, this commit fixes that.

Release v0.8.0

feat: added license text support

The tool now has the ability to add a license header to all code files. This header can be
overwritten by any project. A new nps command, license, along with license.remove had been added to
manage the liecense text in the files. The Husky pre-commit hook now adds the license information to
every file upon commit.

webLibrary has been removed, as it was not used. webLibrary project should be converted to
reactLibrary projects, by wrapping the simple web element into a react one.

BREAKING CHANGE: Uppon commit, every file will end up with a license header

Release v0.7.2

fix(nocode): noCode projects had a problem when trying to run certain tasks

Some tasks were not running do to ome projects lack of a tsconfig.js file. Now this type of projects
also run successfully.

Release v0.7.1

feat: added new type of project - noCode

Now the user is available to select a "noCode" project type. This type of project may be used for
projects that do not require rollup, typescript and otherr tools, yet it still includes the nps
environment.
Additionally, improve over other projects and documentation in general as to be in ync with
the guidelines.

Release v0.7.0

chore: update the version to 0.7.0

BREAKING CHANGE: API changes in regards of names of project types.

fix #14, fix #16

Release v0.6.0

fix: bump version to 0.6.0 and fix minimal errors in husky

This version provides the docs automatic publishing workflow and fixes some bugs in
prepare-commit-msg that ocurred only whenn running commits in some particular ways.

Release v0.5.6

fix: make calls in husky pass through scripts

Now the created projects husky files invoke gobtones-script instead of nps directly.

fix #12, fix #13

Release v0.5.5

build: improve build system to build doc on a separate branch

By creating and additional GitHub action configuration that triggers on every
tag, and updating the corrresponding project settings, now the contents
of GitHub pages should be taken from the action that deploys them.
This implied alo changing the git hooks of the project (that also were documented),
updating the .gitignore to remove the generated docs, and removing some nps
commands that are now not needed.

fix #11

Release v0.5.4

feat: new generated package.json files for all projects

The default contents of package.json files have changed to include a standarized exports and the
typesVerions in all module types. Additionally, change the way in which create and init works, so
that reference to the library name are added to package.json and README files.

fix #8 #9 #10

Release v0.5.3

fix: fix Binary package not being recognized as CommonJS in 0.5.2

Fixed by pointing to a .cjs file instead of a .js file.

fix #7