release-it - CLI release tool for Git repos and npm packages.

  •        45

CLI release tool for Git repos and npm packages. Now you can run npm run release from the command line.

https://github.com/webpro/release-it#release-it
https://github.com/webpro/release-it

Dependencies:

@octokit/rest : 15.2.7
async-retry : 1.2.1
babel-preset-env : 1.6.1
babel-register : 6.26.0
bump-file : 1.0.0
chalk : 2.4.1
conventional-changelog : 1.1.24
conventional-recommended-bump : 2.0.9
cpy : 6.0.0
debug : 3.1.0
globby : 8.0.1
got : 8.3.1
inquirer : 5.2.0
is-ci : 1.1.0
lodash : 4.17.10
mime-types : 2.1.18
ora : 2.1.0
os-name : 2.0.1
parse-repo : 1.0.4
semver : 5.5.0
shelljs : 0.8.1
supports-color : 5.4.0
tmp-promise : 1.0.4
update-notifier : 2.5.0
uuid : 3.2.1
window-size : 1.1.0
yargs-parser : 10.0.0

Tags
Implementation
License
Platform

   




Related Projects

semantic-release - :package::rocket: Fully automated version management and package publishing

  •    Javascript

semantic-release automates the whole package release workflow including: determining the next version number, generating the release notes and publishing the package. This removes the immediate connection between human emotions and version numbers, strictly following the Semantic Versioning specification.

np - A better `npm publish`

  •    Javascript

Support my open source work by buying this excellent Node.js course.Run np without arguments to launch the interactive UI that guides you through publishing a new version.

dry-types - Flexible type system for Ruby with coercions and constraints

  •    Ruby

After checking out the repo, run bin/setup to install dependencies. Then, run bundle exec rake run_specs to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment. To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

python-versioneer - version-string management for VCS-controlled trees

  •    Python

This is a tool for managing a recorded version number in distutils-based python projects. The goal is to remove the tedious and error-prone "update the embedded version string" step from your release process. Making a new release should be as easy as recording a new tag in your version-control system, and maybe making new tarballs. For released software, the version identifier is closely related to a VCS tag. Some projects use tag names that include more than just the version string (e.g. "myproject-1.2" instead of just "1.2"), in which case the tool needs to strip the tag prefix to extract the version identifier. For unreleased software (between tags), the version identifier should provide enough information to help developers recreate the same tree, while also giving them an idea of roughly how old the tree is (after version 1.2, before version 1.3). Many VCS systems can report a description that captures this, for example git describe --tags --dirty --always reports things like "0.7-1-g574ab98-dirty" to indicate that the checkout is one revision past the 0.7 tag, has a unique revision id of "574ab98", and is "dirty" (it has uncommitted changes.


bintray-release - A helper for releasing from gradle up to bintray

  •    Groovy

Super duper easy way to release your Android and other artifacts to bintray. This is a helper for releasing libraries to bintray. It is intended to help configuring stuff related to maven and bintray. At the moment it works with Android Library projects, plain Java and plain Groovy projects, but our focus is to mainly support Android projects.

release - Generate changelogs with a single command

  •    Javascript

When run, this command line interface automatically generates a new GitHub Release and populates it with the changes (commits) made since the last release.You can find an example of how to prepare a release in your project here.

OwncloudPie - Shell script for installing Owncloud on the Raspberry Pi

  •    Shell

Shell script for installing and updating Owncloud on the Raspberry Pi. The script either performs a new installation of the newest Owncloud release or, if already installed, performs an upgrade to the newest release. When doing a new installation, you can choose between the Apache 2 or the NGiNX webserver. The script downloads and installs the latest Owncloud version that can be found in the file at http://owncloud.org/releases/Changelog.

push - Push notifications for cordova (ios, android) browser (Chrome, Safari, Firefox)

  •    Javascript

Push notifications for cordova (ios, android) browser (Chrome, Safari, Firefox) - One unified api on client and server. We are using semantic-release following the AngularJS Commit Message Conventions - Following this pattern will result in better versioning, better changelog and shorter release cycle.

LegacyCura - Read this, it's important! NEW CURA DEVELOPMENT IS HAPPENING AT https://github

  •    Python

Cura development comes with a script "package.sh", this script has been designed to run under *nix OSes (Linux, MacOS, FreeBSD). For Windows the package.sh script can be run from bash using git. The "package.sh" script generates a final release package. You should not need it during development, unless you are changing the release process. If you want to distribute your own version of Cura, then the package.sh script will allow you to do that. The "package.sh" script understands a number of envrionement variables defined at the top of the script. Review and adjust settings to match your needs.

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.

RMT - RMT is a handy tool to help releasing new version of your software

  •    PHP

RMT is a handy tool to help releasing new versions of your software. You can define the type of version generator you want to use (e.g. semantic versioning), where you want to store the version (e.g. in a changelog file or as a VCS tag) and a list of actions that should be executed before or after the release of a new version. Once there, your best option is to pick one of the configuration examples below and adapt it to your needs.

git-pr-release - Release pull request generator

  •    Ruby

Creates a "release pull request", whose body consists of features list or pull requests that are to be released into production. It's especially useful for QA and pre-release checks. git-pr-release automatically collect pull requests merged into master branch and generates the content of the release pull request. All configuration are taken using git config. You can write these variables in file .git-pr-release (instead of .git/config or ~/.gitconfig) to share project-wise configuration to other collaborators.

github-changelog-generator - Automatically generate change log from your tags, issues, labels and pull requests on GitHub

  •    Ruby

Fully automated changelog generation - This gem generates a changelog file based on tags, issues and merged pull requests (and splits them into separate lists according to labels) from GitHub Issue Tracker. To make it easier for users and contributors to see precisely what notable changes have been made between each release (or version) of the project.

vim-fugitive - fugitive.vim: a Git wrapper so awesome, it should be illegal

  •    Vim

View any blob, tree, commit, or tag in the repository with :Gedit (and :Gsplit, :Gvsplit, :Gtabedit, ...). Edit a file in the index and write to it to stage the changes. Use :Gdiff to bring up the staged version of the file side by side with the working tree version and use Vim's diff handling capabilities to stage a subset of the file's changes. :Gblame brings up an interactive vertical split with git blame output. Press enter on a line to edit the commit where the line changed, or o to open it in a split. When you're done, use :Gedit in the historic buffer to go back to the work tree version.

gem-release - Release your ruby gems with ease.

  •    Ruby

This gem plugin aims at making gem development easier by automating repetitive work based on conventions, configuration, and templates. It adds the commands bootstrap, gemspec, bump, tag and a release to the rubygems gem command.

FullPageOS - A raspberrypi distro to display a full page browser on boot

  •    Shell

A Raspberry Pi distribution to display one webpage in full screen. It includes Chromium out of the box and the scripts necessary to load it at boot. This repository contains the source script to generate the distribution out of an existing Raspbian distro image. FullPageOS supports building variants, which are builds with changes from the main release build. An example and other variants are available in the folder src/variants/example.

goreleaser - Deliver Go binaries as fast and easily as possible

  •    Go

Deliver Go binaries as fast and easily as possible.GoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. All that wrapped in your favorite CI.

node-fibers - Fiber/coroutine support for v8 and node.

  •    C++

Fibers, sometimes called coroutines, are a powerful tool which expose an API to jump between multiple call stacks from within a single thread. This can be useful to make code written for a synchronous library play nicely in an asynchronous environment. Note: node-fibers uses node-gyp for building. To manually invoke the build process, you can use node-gyp rebuild. This will put the compiled extension in build/Release/fibers.node. However, when you do require('fibers'), it will expect the module to be in, for example, bin/linux-x64-v8-3.11/fibers.node. You can manually put the module here every time you build, or you can use the included build script. Either npm install or node build -f will do this for you. If you are going to be hacking on node-fibers, it may be worthwhile to first do node-gyp configure and then for subsequent rebuilds you can just do node-gyp build which will be faster than a full npm install or node-gyp rebuild.

shellfire - A repository of namespaced, composable shell (bash, sh and dash) function libraries

  •    Shell

shellfire consists of a number of github repositories, called modules. Each module contains functions or resources in a specific namespace. You create a shellfire application by making a new repository (typically on GitHub) with a skeleton structure, and then adding the modules you need. You populate a template shell script, and then just code away. It couldn't be easier. shellfire scripts work straightaway from source control. When you're ready to do a release, you can use fatten to make a standalone script, and swaddle to then deploy it to GitHub releases, pages, etc as tarballs, debs, etc. Try the overdrive tutorial. You'll be up and running with your first shellfire application in 10 mins.