Displaying 1 to 20 from 23 results

cz-cli - The commitizen command line utility.

  •    Javascript

When you commit with Commitizen, you'll be prompted to fill out any required commit fields at commit time. No more waiting until later for a git commit hook to run and reject your commit (though that can still be helpful). No more digging through CONTRIBUTING.md to find what the preferred format is. Get instant feedback on your commit message formatting and be prompted for required fields. Now, simply use git cz instead of git commit when committing.

next-update - Tests if module's dependencies can be updated to latest version

  •    Javascript

Note I no longer maintain Node 0.12/4 compatibility. Please switch to Node 6. Both package.json file and node_modules folder are left unchanged, and now you know that you can safely upgrade both libraries to later versions.

semver - Semantic Versioning (semver) library written in golang

  •    Go

semver is a Semantic Versioning library written in golang. It fully covers spec version 2.0.0. Note: Always vendor your dependencies or fix on a specific version tag.

rock - Create semantic version tags for your Go packages, search and discover new packages

  •    Go

The rock command allows you to tag your code with releases that conform to semantic versioning easily.The rock tool search function uses gopher.rocks which holds metadata about Go packages.

axion-release-plugin - Gradle release & version management plugin.

  •    Groovy

Releasing versions in Gradle is very different from releasing in Maven. Maven came with maven-release-plugin which did all the dirty work. Gradle has no such tool and probably doesn't need it anyway. Evolution of software craft came to the point, when we start thinking about SCM as ultimate source of truth about project version. Version should not be hardcoded in pom.xml or build.gradle.axion-release-plugin embraces this philosophy. Instead of reading project version from buildfile, it is derived from nearest tag in SCM (or set to default if nothing was tagged). If current commit is tagged commit, project has a release version. If there were any commits after last tag, project is in SNAPSHOT version. This very simple and intuitive philosophy, alongside with Semantic Versioning rules, makes it a lot easier to manage project versions along SCM tag versions.

SyntacticVersioning - Helper tool to verify semantic version changes based on API surface area changes

  •    F#

Be able to get an idea about the semantic version changes based on the surface area changes of a .net assembly.Developers should be able to use the tool to give a magnitude of any API changes. This is helpful when pushing NuGet-packages from a continuous integration server. Internally used NuGet packages of a .net developer organisation often focus on delivering on business goals; the versioning is easily forgotten. I.e. we want to be able to use this from TeamCity and others.

ngc - NewGoCommand - An opinionated and lightweight project starter. (WORK IN PROGRESS)

  •    Go

ngc is an opinionated helper utility that creates some boilerplate for a new Go command or package. Run ngc in an empty directory. IT WILL OVERWRITE THINGS RIGHT NOW In the future, it may move existing files or directories that would have been overwritten.

ngp - New Go Package

  •    Go

ngp is an opinionated helper utility that creates some boilerplate for a new Go command or package. Run ngp in an empty directory. IT WILL OVERWRITE THINGS RIGHT NOW In the future, it may move existing files or directories that would have been overwritten.

gradle-semantic-build-versioning - Gradle plugin to generate version-numbers and tags using semantic versioning

  •    Groovy

NOTE: Version 4.x and above will no-longer support Java 7 due to the fact that addressing certain issues requires upgrading the JGit dependency, which now supports only Java 8 and above. Version 3.x will still work on Java 7 and above, but will unfortunately have the aforementioned known issues. Documentation for 3.x can be found here. NOTE: Plugin configuration and usage has changed significantly since version 2.x. If you are still using that version, the documentation can be found here. This is a Gradle plugin that provides support for semantic versioning of builds. It is quite easy to use and extremely configurable. The plugin allows you to bump the major, minor, patch or pre-release version based on the latest version, which is identified from a git tag. It also allows you to bump pre-release versions based on a scheme that you define. The version can be bumped by using version-component-specific project properties or can be bumped automatically based on the contents of a commit message. If no manual bumping is done via commit message or project property, the plugin will increment the version-component with the lowest precedence; this is usually the patch version, but can be the pre-release version if the latest version is a pre-release one. The plugin does its best to ensure that you do not accidentally violate semver rules while generating your versions; in cases where this might happen the plugin forces you to be explicit about violating these rules.

Version - Represent and compare versions via semantic versioning (SemVer) in Swift

  •    Swift

Version is a Swift Library, which enables to represent and compare semantic version numbers. It follows Semantic Versioning 2.0.0. Besides UIKit's UIDevice the more preferable variant to access the operation system version in Foundation as shown below is supported, too.

next-ver - Tells you the next semantic version for your local package

  •    Javascript

Imagine a local package with current version 2.3.0 and a single semantic commit fix(something): fix the login. This tools computes the next version that should be used. Then you can publish, for example using npm version command or one of the good helper CLI tools, like publish-please, np or ci-publish.

simple-commit-message - Simple commit message wizard and validator; works with commitizen and pre-git

  •    Javascript

If you just want to commit code, but not publish a new version from CI, you have several choices. note if you have local commit message validation as a Git hook, for example using pre-git skip the message check using git commit -n option.

gradle-release-plugin - Gradle plugin providing very minimal release version numbering (Git-specific)

  •    Groovy

Gradle plugin providing very minimal release version numbering. The plugin assumes a MAJOR.MINOR.PATCH[-SNAPSHOT] version pattern kept in a version.txt file.

codelog - A simple ruby gem to manage Changelogs.

  •    Ruby

A gem to help big teams to manage their chagelogs. When many people are developing changes to compose one product release, there can be some conflicts on merging the changes added to the Changelog. These conflicts can be badly resolved by git, which could cause lost of important release notes.

smooth-release - Replacement for `npm version` and `npm publish` with validations and CHANGELOG

  •    Javascript

Smart CLI utility to safely and automatically do every step to release a new version of a library hosted on GitHub and published on npm. smooth-release automatically detects if the next version should be "breaking" or not. If a version is "breaking" it will be a major otherwise it will be a patch. smooth-release never creates a minor version.

bump - :sunflower: CLI tool to help draft a GitHub Release for the next semantic version

  •    Go

Simple, cross-platform CLI tool to help draft a GitHub Release for the next semantic version of your project. This is intentionally designed to work with the GitHub web site interface for drafting releases, and does not even require you to have the source code checked out locally.

release-tool - Command line tool for releasing new versions of a project

  •    PHP

Inspired by Liip RMT, this release tool helps you to automate the release of new versions of your software. It is written in PHP but can be used for any type of project, as long as you have PHP installed on your machine. The recommended method of installing this package is using a phar file. This is because installing using Composer can possibly cause dependency conflicts. You can download the most recent phar from the Github Releases page.

semantics - A utility written in Golang to automatically handle Semantic Versioning in a CI environment

  •    Go

A utility written in Golang to automatically handle Semantic Versioning in a CI environment. Check out the wiki for more information on using semantics.

git-semv - 🔖 Git plugin for Semantic Versioning

  •    Go

git-semv: This is a Git plugin for Semantic Versioning. The usefulness of Semantic Versioning has been accepted by OSS in advance. And, with the appearance of Go modules, Semantic Versioning became indispensable for the development of the Go library. However, git tag used for versioning can not support pre-releases and sorts including build information for managing Semantic Versioning. Also, it is not easy to increment the version. This git-semv is a CLI tool for solving these problems and functions as git subcommand.

We have large collection of open source products. Follow the tags from Tag Cloud >>

Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.