npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

semantic-release-preconfigured-conventional-commits

v1.1.115

Published

Shareable configuration for Semantic Release with Conventional Commits https://www.conventionalcommits.org/

Downloads

16,084

Readme

Pre-configured shareable Semantic Release configuration for conventional commits

npm version

This is a ready-to-use, pre-defined configuration for semantic-release, meant to support the use of conventional commits along with Whitesource Renovate.

Configuration

MAJOR release

  • Any commit type and scope terminating with ! causes a BREAKING CHANGE

MINOR release

  • Commit type chore with scope api-deps (Dependency updates)
  • Commit type feat (Features) with any scope

PATCH release

  • Commit type chore with scope core-deps (Dependency updates)
  • Commit type fix (Bug Fixes) with any scope
  • Commit type docs (Documentation) with any scope
  • Commit type perf (Performance improvements) with any scope
  • Commit type revert (Revert previous changes) with any scope

No release

  • Commit type test (Tests)
  • Commit type ci (Build and continuous integration)
  • Commit type build (Build and continuous integration)
  • Commit type chore with scope deps (Dependency updates)
  • Commit type chore (General maintenance) with scopes different than the ones mentioned above
  • Commit type style (Style improvements) with any scope
  • Commit type refactor (Refactoring) with any scope

Usage

To use this configuration, add to your package.json:

  "devDependencies": {
    "semantic-release-preconfigured-conventional-commits": "latest"
  }

(actually, pick the latest stable version)

The configuration sets up and pre-applies semantic-release/commit-analyzer, semantic-release/release-notes-generator, and semantic-release/changelog.

These are usually always present, but rarely enough.

Then, the recommended way to exploit this pre-configuration is through a release.config.js file in the project root; the reason is that currently the semantic release extension mechanism does not merge the configurations in-depth, thus, adding further plugins results in the configuration being ignored.

A minimal release.config.js for creating releases on GitHub, for instance, looks like:

var config = require('semantic-release-preconfigured-conventional-commits');
config.plugins.push(
    "@semantic-release/github",
    "@semantic-release/git",
)
module.exports = config

It can be easily enriched to account for more elaborate workflows, as, for instance:

var publishCmd = `
IMAGE_NAME="danysk/docker-manjaro-texlive-ruby"
docker build -t "$IMAGE_NAME:\${nextRelease.version}"
docker push --all-tags "$IMAGE_NAME"
`
var config = require('semantic-release-preconfigured-conventional-commits');
config.plugins.push(
    [
        "@semantic-release/exec",
        {
            "publishCmd": publishCmd,
        }
    ],
    "@semantic-release/github",
    "@semantic-release/git",
)
module.exports = config

Proposing changes

I gladly consider changes to the configuration. In case you think something is missing or deserves to be changed, open an issue.