Displaying 1 to 20 from 23 results

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.

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.

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.




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.

pyscaffold - Python project template generator with batteries included

  •    Python

you are all set and ready to go. All configuration can be done in setup.cfg like changing the description, url, classifiers, installation requirements and so on as defined by setuptools. That means in most cases it is not necessary to tamper with setup.py.

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.


shipkit - Toolkit for shipping it used by Mockito library

  •    Java

You will be more productive if your releases are fully automated and happen on every change. You will build great product if you can focus on code & features, but not on the release overhead. Shipkit will make it happen. Shipkit is a toolkit for shipping it.Imagine the world where you call pull in a new version of some Open Source library and not worry if it breaks compatibility. Imagine that you can submit a pull request to some project, have it reviewed timely, and have the new version with your fix available to you in minutes after your PR is merged. Imagine that for any dependency you consider upgrading, you can view its neatly and consistently maintained release notes. Imagine that you can set up practical Continuous Delivery automation in your project in minutes, by using a well behaving and documented Gradle plugin. Imagine that you can focus on code and features while the release management, versioning, publishing, release notes generation is taken care for you automagically.

sbt-sonatype - A sbt plugin for publishing Scala/Java projects to the Maven central.

  •    Scala

A sbt plugin for publishing your project to the Maven central repository through the REST API of Sonatype Nexus. Deploying artifacts to Sonatype repository is a requirement for synchronizing your projects to the Maven central repository. sbt-sonatype plugin enables two-step release of Scala/Java projects. Set Sonatype account information (user name and password) in the global sbt settings. To protect your password, never include this file within your project.

Devtools - The Hoa\Devtools library.

  •    PHP

Hoa is a modular, extensible and structured set of PHP libraries. Moreover, Hoa aims at being a bridge between industrial and research worlds. This library contains several development tools. This is for developers or maintainers. Sometimes it can be useful to users also, but in particular cases.

artifactory-debian - :wrench: :package: Tools to use Artifactory as a Debian (APT) repository, and dput DEB packages into it, or upload them to Bintray

  •    Python

artifactory-debian offers tools to use Artifactory as a Debian (APT) repository, and conveniently upload DEB packages to Artifactory or Bintray. Also see the wiki. Principles of Continuous Delivery mandate that you propagate a binary artifact, once it's built, unchanged through the different quality gates and deployment stages of your delivery pipeline. The need for keeping them in ideally a single place becomes obvious pretty fast, together with similar build artifacts like Java JARs.

git-release-name - Generate a release names based on a git sha

  •    Rust

A simple tool that takes a sha and returns a random name for the release. The name will be deterministic based on the version of the tool. This project is broken into three crates. Each crate provides a different interface to the dictionary. The main library with functionality is the libray (found in rn-dictionary). The other two are rn-cli and rn-web. Repo is licensed under MIT.

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.

bin - 💻 Automatically download latest GitHub release binaries (for your OS/arch) using wget or curl

  •    Go

This is a simple server (deployed @ https://bin.suyash.io) that makes it easy to download the latest binary associated with any GitHub repo release using regular old wget and curl. It attempts to use your User-Agent to fetch the right GitHub release asset for your OS/arch, but also lets you provide query parameters to specify OS/arch, and optionally uncompress the release artifact on the fly. I mostly just built this as a way to distribute my software binaries easily without dealing with brew, npm, etc (though they certainly have their advantages & trust). I can just give my users a one line download link that will always get them the latest released binary for their platform, and all I have to do is just update GitHub releases like I normally do.

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.

craft - The universal Sentry release CLI

  •    TypeScript

craft is a command line tool that helps to automate and pipeline package releases. It suggests, and then enforces a specific workflow for managing release branches, changelogs, artifact publishing, etc. craft requires a few environment variables to be present in order to function properly.