Search Results for "marbel-release"

...It's recommended you use the high-level standard-version library, which is a drop-in replacement for npm's version command, handling automated version bumping, tagging, and CHANGELOG generation. Alternatively, if you'd like to move towards completely automating your release process as an output from CI/CD, consider using semantic-release. We specifically limit our support to LTS versions of Node, not because this package won't work on other versions, but because we have a limited amount of time, and supporting LTS offers the greatest return on that investment. It's possible this package will work correctly on newer versions of Node. ...

Ensures you are publishing from your release branch (main and master by default). Ensures the working directory is clean and that there are no unpulled changes. Reinstalls dependencies to ensure your project works with the latest dependency tree. Ensures your Node.js and npm versions are supported by the project and its dependencies. Bumps the version in package.json and npm-shrinkwrap.json (if present) and creates a git tag.

List all available Node.js versions. Sorted from the most to the least recent. Includes major release and LTS information. This package is an ES module and must be loaded using an import or import() statement, not require(). The return value resolves to an object with the following properties. List of available Node.js versions and related information. Sorted from the most to the least recent Node.js version. List of Node.js major releases sorted from the most to the least recent.