@rob.hameetman/semantic-release-config v1.0.0

📦 @rob.hameetman/semantic-release-config

§1: Overview

This is a semantic-release config used in NPM packages designed for automation and easier prerelease management. Configs create a prerelease version with each PR/branch and allow flexible configuration through environment variables.

PR Prerelease Strategies

Default preid/channel types can be configured by setting the RELEASE_PR_PRERELEASE_STRATEGY environment variable to one of the following values:

Customizable Preids & Channels

Preids and channels can be easily customized by setting the RELEASE_PR_PRERELEASE_PREID and RELEASE_PR_PRERELEASE_CHANNEL environment variables. Each has access to the following dictionary for customization:

This table shows examples of each as well as the resulting preid/channel:

Optional Labels

The preid label can be customized with the RELEASE_PR_PRERELEASE_LABEL environment variable. Setting the value to "omit" will remove the label from the prerelease preid.

§2: Getting Started

Follow these steps to get the project up and running on your local machine:

1. Prerequisites

• Node v20+
• NPM v9+

2. Installation

git clone git@github.com:RobHameetman/semantic-release-config
cd semantic-release-config
npm run setup

3. Editor Configuration

For VSCode, save the following as editor.code-workspace in the project root directory:

{
  "folders": [
    {
      "path": "."
    }
  ],
  "settings": {
    "editor.rulers": [
     80,
     120
    ],
    "eslint.nodeEnv": "development",
    "files.autoSave": "onFocusChange",
    "yaml.format.enable": true,
    "yaml.format.singleQuote": true,
  },
}

§3: Development

NPM Commands

• npm run build: Create a production build artifact.
• npm run format: Perform static analysis and auto-fix errors.
• npm run reset: Perform a full node_modules/ reset.
• npm test: Execute the Jest test suite.

Environment Variables

General Options

Release Rules

Custom Commands

Configuration-specific

^1: Release rules for the angular preset are already included. ^2: This path is relative to the path from which semantic-release is running. For example if semantic-release runs from /my-project and execCwd is set to buildScripts then the shell command will be executed from /my-project/buildScripts. ^3: Uses /bin/sh on UNIX and cmd.exe on Windows. A different shell can be specified as a string. The shell should understand the -c switch on UNIX or /d /s /c on Windows.

§4: Testing

This project uses the following tiers of testing:

• Unit & Integration Tests: Use npm run test to run all tests.

These commands accept additional inputs following a -- modifier as in the common use-case examples below:

• npm run test -- --watch: Watch for changes and re-run all tests.
• npm run test -- src/path/to/test.spec.ts: Run tests in a specific test file.

§5: Publishing

Creating and merging PRs will create new package versions that you can monitor by vising the Actions tab in Github.

Channels

• alpha: Used for manual testing in other packages
• beta: Used for UAT and testing by external consumers
• next: Everything that will be included in the next major version release

Versioning

This project uses SemVer for versioning. For the versions available, see the tags on this repository.

An beta pre-release version will be published whenever you create a PR and incremented as you update your changes. Once the PR is merged, a release version is created automatically. This is handled with semantic-release.

Major versions should have a corresponding release in Github. Click here to create a new release once your version meets acceptance criteria.

§6: Contact

For inquiries and additional information, please reach out to:

Rob Hameetman
Front End Architect | Chicago, IL
engineering@robhameetman.com

§7: License

Distributed under the MIT License.
See the LICENSE file for details.