npm-ci-demo
Advanced tools
This is an exercise about continuous delivery of NPM library or software.
By Semantic Versioning 2.0.0, a version number is in format of MAJOR.MINOR.PATCH. However, by semantic-release, they are also called Breaking, Feature and Patch.
The following tools are used in our exercise:
npm install -g semantic-releaseYou should have all these tools installed before doing exercise. And, you should have accounts on:
Create a new repository on github.com, then clone it into your local store:
# Suppose the repository is YounGoat/npm-ci-demo
git clone https://github.com/YounGoat/npm-ci-demo.git
Initiate the repository's root direction as an NPM project.
cd npm-ci-demo
npm init
# Then to fill out as prompted.
... to be continued ...
tools, protocols and standards:
others:
FAQs
an exercise about continuous delivery of npm module
We found that npm-ci-demo demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.