PACKAGING IS HARD

Releasing a new version of your Ruby/Node/Python libary sounds simple, just bump the version in the metadata file and push it to the community repo.

But in reality, it's not that simple. Depending on your language there could be a dozen steps required before you can get your shiny new library in the hands of other developers.

PACKAGR CAN HELP

It doesn't need to be this difficult. Modern software development has completely bought into the benefits of testing and Continuous Integration. Packagr builds ontop of your existing CI and automates all the steps between recieving that PR and publishing a new version of your software.

Basically it's is a generic Continuous Delivery pipeline for versioned artifacts, and it works with libraries written in any language.

FEATURES

Packagr is highly configurable, and every step can be customized to fit your needs. Having said that, it's pre-configured with an opinionated set of steps that follow the best practices of each language.

• Semver versioning
• Version bumping (major/minor/patch)
• (Re)generate shrinkwrap/lock files
• Verifies dependencies still exist (#Nodepocalypse)
• Uploads to community (RubyGems/PyPi/..)
• Runs all unit tests/code coverage
• Minifies source
• Linting
• Changelog updates
• Tags new versions in Git
• Creates Github releases & artifacts
• Validates library file structure