🔐 Versionguard

Diverging core dependencies between multiple applications are a thing of the past! Versionguard is here to protect your applications from out of sync dependencies - on your terms!

npm i @johanneslumpe/versionguard -g

📋 Features

• 🎉 Manage blessed dependency versions across multiple applications with ease
• 📋 Multiple application groups with multiple dependency sets for tailored version governance
• ⏰ Grace periods allow for staggered upgrading
• 🚦 Tiered version checking: pass, tentantive pass and fail
• ⚡️ Automatically fail builds on CI when dependencies are out of date

\

📖 Available Commands

Version Checking

check

\

This command is at the heart of version guard. It will ensure that none of your applications diverge from the allowed ranges for registered dependencies. When your dependencies do not satify the requirements the CLI will exit with a non-zero exit code. This is useful if you'd for example like to automatically fail builds on CI. Explore all commands below to learn how to set up a configuration which you can use with check.

Groups

groups:add <groupname>

\

This commands lets you add a group to your config file. A group is the basic building block of a versionguard config. It contains your applications and your dependency sets. A version check can be run on a group as a single unit.

groups:remove <groupname>

In the same way that you can add groups, you can remove them as well!

groups:rename <oldname> <newname>

\

Want to rename a group? Sure we can do that! The above command will allow you to rename your group to anything you want, given that the new name isn't taken yet by another group.

groups:list

\

If you forgot which groups you have added to versionguard, groups:list is your friend and will gladly list them for you!

groups:info <groupname>

\

More detailed information about a group, e.g. applications added and available dependency sets can be retrieved using groups:info <groupname>.

Applications

applications:add <groupname> <applicationpaths..>

\

A group isn't useful without applications added to it. Using this command you can add as many applications as you'd like to a group. The paths need to be relative to your versionguard config file's location and must contain a valid package.json file.

applications:remove <groupname> <applicationpaths..>

\

It's sad but sometimes applications are obsolete and then there is no place for them in your versionguard config file anymore. Get rid of them!

Dependencies

dependencies:create-set <groupname> <setname>

\

In addition to applications you will also need to declare at least one dependency set in order to get value out of versionguard. Do that with this command!

dependencies:delete-set <groupname> <setname>

\

If you ever get tired of a dependency set, just remove it!

dependencies:add <groupname> <setname> <dependency>

\

Without any dependencies in a set, what's the point? You ought to check at least something. Add dependencies using this command. In case the dependency already exists in the set you want to add it to, its version will be updated to whatever the version is you wanted to add. If you rock multiple dependency sets, for example for public and private dependencies, and add a dependency which already exists in another set, versionguard will assist you by asking if you'd like to automatically migrate that dependency.

dependencies:remove <groupname> <setname> <dependency>

\

If you or your team decides that it's time for a dependency to be removed that's fine, get rid of it! It was outdated anyway.

dependencies:grace-period <groupname> <setname> <graceperiod>

\

In case you'd like to give yourself and others a bit of leeway until when a dependency needs to be in line with the newly required version, you can use this command to set a grace period. Conversely you can also force people to instantly upgrade by setting a grace period of 0.

Options

Apart from the core commands listed above, versionguard also provides some options:

--verbose

If you want verbose output, use this flag. Conflicts with --json flag

--json

In case you want to use the command result for further tasks, you can use this flag to get raw JSON output instead of formatted log messages. Conflicts with --verbose flag

--config-path

By default, versionguard will search for a config file from the current working directory upwards. If it cannot find a config it will conveniently create one for you. In case you want to reference a config file that is not within a directory in the tree above your working directory, you can use this flag to pass a config file path.

📄 License

versionguard is MIT licensed, as found in the LICENSE file.