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

  •        100

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.

https://github.com/semantic-release/semantic-release#readme
https://github.com/semantic-release/semantic-release

Dependencies:

@semantic-release/commit-analyzer : ^6.1.0
@semantic-release/error : ^2.2.0
@semantic-release/github : ^5.1.0
@semantic-release/npm : ^5.0.5
@semantic-release/release-notes-generator : ^7.1.0
aggregate-error : ^1.0.0
cosmiconfig : ^5.0.1
debug : ^4.0.0
env-ci : ^3.0.0
execa : ^1.0.0
figures : ^2.0.0
find-versions : ^2.0.0
get-stream : ^4.0.0
git-log-parser : ^1.2.0
git-url-parse : ^10.0.1
hook-std : ^1.1.0
hosted-git-info : ^2.7.1
lodash : ^4.17.4
marked : ^0.5.0
marked-terminal : ^3.0.0
p-locate : ^3.0.0
p-reduce : ^1.0.0
read-pkg-up : ^4.0.0
resolve-from : ^4.0.0
semver : ^5.4.1
signale : ^1.2.1
yargs : ^12.0.0

Tags
Implementation
License
Platform

   




Related Projects

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.

omniauth-saml - A generic SAML strategy for OmniAuth

  •    Ruby

We tag and release gems according to the Semantic Versioning principle. In addition to the guidelines of Semantic Versioning, we follow a further guideline that otherwise backwards-compatible dependency upgrades for security reasons should generally be cause for a MINOR version upgrade as opposed to a PATCH version upgrade. Backwards-incompatible dependency upgrades for security reasons should still result in a MAJOR version upgrade for this library. For IdP-initiated SSO, users should directly access the IdP SSO target URL. Set the href of your application's login link to the value of idp_sso_target_url. For SP-initiated SSO, link to /auth/saml.

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.

PodsUpdater - A macOS app which helps you manage dependency releases in your Podfile.

  •    Swift

I believe it should be up to the developer to determine the exact versions of dependencies used in their projects. When adding Pods to the Podfile, most developers use the optimistic operator pod 'RxSwift', '~> 4.1.1' or even leave out the version information entirely pod 'RxSwift'. This is because no one wants to go through the hell of finding new versions of their dependencies and updating manually. This also means the Dependency manager(CocoaPods) will have to decide which version to install in your project. Granted, with the optimistic operator, CocoaPods would probably never install a version of the Pod with breaking changes as long as the framework's developer continues using semantic versioning. But then, you wouldn't even get to know about the breaking release at all.


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.

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.

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.

EnergyPlus - EnergyPlus™ is a whole building energy simulation program that engineers, architects, and researchers use to model both energy consumption and water use in buildings

  •    C++

This is the EnergyPlus Development Repository. EnergyPlus™ is a whole building energy simulation program that engineers, architects, and researchers use to model both energy consumption and water use in buildings. EnergyPlus is typically released twice annually, usually in March and September. It is recommended all use of EnergyPlus is production workflows use these formal, public releases. Iteration (pre-)releases may be created during a development cycle, however users should generally avoid these, as input syntax may change which won't be supported by the major release version transition tools, and could require manual intervention to remedy. If an interim release is intended for active use by users, such as a bug-fix-only or performance-only re-release, it will be clearly specified on the release notes and a public announcement will accompany this type of release.

unity - This repository contains development environment for the entire package

  •    

Version 4.x is dead. Loss of original signing certificate made it impossible to release anything compatible with v4.0.1 release. To give original developers a credit only about 60 issues were found during two years in production. To move on and enable further development version v5 has been created.Version 5.x is created as replacement for v4.0.1. Assemblies and namespaces are renamed and refactored but otherwise it is compatible with the original. v5.0.0 release fixes most of the issues found in v4.0.1 and implements several optimizations but the accent was on compatibility and if optimization would break API it was ommited. Once stabilized, this version will enter LTS status and will be patched and fixed for the next few years. There will be no significant development in this line.

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.

react-lifecycles-compat - Backwards compatibility polyfill for React class components

  •    Javascript

React version 17 will deprecate several of the class component API lifecycles: componentWillMount, componentWillReceiveProps, and componentWillUpdate. (Read the Update on Async rendering blog post to learn more about why.) A couple of new lifecycles are also being added to better support async rendering mode. Typically, this type of change would require third party libraries to release a new major version in order to adhere to semver. However, the react-lifecycles-compat polyfill offers a way to use the new lifecycles with older versions of React as well (0.14.9+) so no breaking release is required. This enables shared libraries to support both older and newer versions of React simultaneously.

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.

alexa-app-server - An Alexa app server for alexa-app.

  •    Javascript

An Alexa App (Skill) Server module using Node.js and the alexa-app module. You're reading the documentation for the next release of alexa-app-server, which should be 3.0.3. Please see CHANGELOG and make sure to read UPGRADING when upgrading from a previous version. The current stable release is 3.0.2.

gradle-release - gradle-release is a plugin for providing a Maven-like release process for projects using Gradle

  •    Groovy

Please refer to the Gradle DSL PluginDependenciesSpec to understand the behavior and limitations when using the new syntax to declare plugin dependencies. After you have your build.gradle file configured, simply run: gradle release and follow the on-screen instructions.

release-drafter - Drafts your next release notes as pull requests are merged into master.

  •    Javascript

Drafts your next release notes as pull requests are merged into master. Built with Probot. Release Drafter also supports Probot Config, if you want to store your configuration files in a central repository. This allows you to share configurations between projects, and create a organization-wide configuration file by creating a repository named .github and file named release-drafter.yml.

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.

sbt-release - A release plugin for sbt

  •    Scala

This sbt plugin provides a customizable release process that you can add to your project. Notice: This README contains information for the latest release. Please refer to the documents for a specific version by looking up the respective tag.

Open Information Integration

  •    Java

Open Information Integration Tool Suite (Open II) is used by analysts and programmers to accelerate data integration and harmonization across organizations. OpenII has a neutral schema repository for browsing and comparing all sorts of data models. Release Notes Release Date: March 29, 2012 Build Version: 1.0.2639 Notes: 1. Build version numbers are now displayed in the tool suit's About OpenII page. 2. Access to new features in the Unity tool, a vocabulary editor, is now available. In add