From f0e28171f4b5396c28e204759dca5bf0dcb7dbd3 Mon Sep 17 00:00:00 2001 From: Grey Baker Date: Sat, 23 Jun 2018 17:52:12 -0400 Subject: [PATCH] Add SemVer stability badge to README --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 41bc3545e..56a40f24b 100644 --- a/README.md +++ b/README.md @@ -7,9 +7,9 @@ fog is the Ruby cloud services library, top to bottom: * Mocks make testing and integrating a breeze. [![Build Status](https://secure.travis-ci.org/fog/fog.svg?branch=master)](http://travis-ci.org/fog/fog) -[![Dependency Status](https://gemnasium.com/fog/fog.svg)](https://gemnasium.com/fog/fog) [![Code Climate](https://codeclimate.com/github/fog/fog/badges/gpa.svg)](https://codeclimate.com/github/fog/fog) [![Gem Version](https://badge.fury.io/rb/fog.svg)](http://badge.fury.io/rb/fog) +[![SemVer](https://api.dependabot.com/badges/compatibility_score?dependency-name=fog&package-manager=bundler&version-scheme=semver)](https://dependabot.com/compatibility-score.html?dependency-name=fog&package-manager=bundler&version-scheme=semver) ## Dependency Notice @@ -17,10 +17,10 @@ Currently all fog providers are getting separated into metagems to lower the load time and dependency count. If there's a metagem available for your cloud provider, e.g. `fog-aws`, -you should be using it instead of requiring the full fog collection to avoid +you should be using it instead of requiring the full fog collection to avoid unnecessary dependencies. -'fog' should be required explicitly only if the provider you use doesn't yet +'fog' should be required explicitly only if the provider you use doesn't yet have a metagem available. ## Getting Started