chore(release): v2.1.0 #913
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes this PR introduce ?
Cache dependenciesstep in CI so hopefully it solves the issue with the CI failing (as discussed in Gitter chat)sqlite3from5.0.1to5.0.0sincesqlite3@5.0.1have issues. See: Failed at the sqlite3@5.0.1 install script. TryGhost/node-sqlite3#1424huskyso everytime we commit, it verify the commit message, and runnpm run lintalso to avoid installing husky when installing the package, we usepinstmade by the creator ofhusky. See: https://github.com/typicode/pinstrelease-itandcommitlintso it generates the changelog automatically based on commit messages also automatically choose the version number to increase based on semver.markdownlint, see: https://github.com/DavidAnson/markdownlintREADME, so we only display how to use the package for the current latest version, if users want to know how to use it for older versions of TypeScript they can see in the Changelog.Is there anything you'd like reviewers to focus on?
Once this PR has been merged, we could create a new release on GitHub, so it automatically release a new version on
npmif you set correctlyNPM_TOKENsecret as it was suggested in this PR: #871.We should use https://github.com/zeke/semantic-pull-requests.
Note: Git is showing a large number of changes but in fact, it's because I installed a few new dependencies so
package-lock.jsonhas lot of changes.