https://github.com/purpleclay/nsv

Semantic versioning without any config
https://github.com/purpleclay/nsv

conventional-commits git go no-config semantic-versioning semver semver-release

Last synced: 24 days ago
JSON representation

Semantic versioning without any config

• Host: GitHub
• URL: https://github.com/purpleclay/nsv
• Owner: purpleclay
• License: mit
• Created: 2023-03-23T10:56:33.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-05-16T05:35:22.000Z (6 months ago)
• Last Synced: 2024-05-17T00:27:50.961Z (6 months ago)
• Topics: conventional-commits, git, go, no-config, semantic-versioning, semver, semver-release
• Language: Go
• Homepage: https://docs.purpleclay.dev/nsv/
• Size: 4.02 MB
• Stars: 4
• Watchers: 2
• Forks: 0
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md
  • Codeowners: .github/CODEOWNERS

Awesome Lists containing this project

README

        
# NSV

NSV (Next Semantic Version) is a convention-based semantic versioning tool that leans on the power of conventional commits to make versioning your software a breeze!

## See it in action

https://github.com/purpleclay/nsv/assets/106762954/4d3362ac-6b1c-42b1-a13a-0edffb2ab6bd

## Why another versioning tool

There are many semantic versioning tools already out there! But they typically require some configuration or custom scripting in your CI system to make them work. No one likes managing config; it is error-prone, and the slightest tweak ultimately triggers a cascade of change across your projects.

Step in NSV. Designed to make intelligent semantic versioning decisions about your project without needing a config file. Entirely convention-based, you can adapt your workflow from within your commit message.

The power is at your fingertips.

### Features

- First-class support for semantic versioning. Conventional commits help give it a nudge in the right direction.

- Configure your Conventional Commit prefixes for complete control.

- If you batch your commits per release or prefer a continuous delivery approach, it has you covered.

- Context-aware, it automatically switches to a monorepo workflow.

- Extend the power of your commits through commands to dynamically change your semantic release workflow.

- Patch files with the next semantic version for that complete release workflow.

- Get up and running in seconds within GitHub and GitLab with the available [action](https://github.com/purpleclay/nsv-action) or [template](https://gitlab.com/purpleclay/nsv).

- First class [Dagger](https://dagger.io/) support.

## Documentation

Check out the latest [documentation](https://docs.purpleclay.dev/nsv/)

## Badges

[![Build status](https://img.shields.io/github/actions/workflow/status/purpleclay/nsv/ci.yml?style=flat-square&logo=go)](https://github.com/purpleclay/nsv/actions?workflow=ci)

[![License MIT](https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square)](/LICENSE)

[![Go Version](https://img.shields.io/github/go-mod/go-version/purpleclay/nsv.svg?style=flat-square)](go.mod)

[![DeepSource](https://app.deepsource.com/gh/purpleclay/nsv.svg/?label=active+issues&token=1JHae42sEcDRhZdEe-tfiPEv)](https://app.deepsource.com/gh/purpleclay/nsv/?ref=repository-badge)