Version 2.2.1

yeisonvargasf · yeisonvargasf · commit d41e98c4ceb3 · 2022-10-04T16:01:17.000-05:00
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,6 +5,11 @@ All notable changes to this project will be documented in this file.
 The format is partly based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html) and [PEP 440](https://peps.python.org/pep-0440/)
 
+## [2.2.1] - 2022-10-04
+- Fixed the use of the SAFETY_COLOR environment variable
+- Fixed bug in the case of vulnerabilities without a CVE linked
+- Fixed GitHub version in the README
+
 ## [2.2.0] - 2022-09-19
 - Safety starts to use dparse to parse files, now Safety supports mainly Poetry and Pipenv lock files plus other files supported by dparse.
 - Added logic for custom integrations like pipenv check.
diff --git a/README.md b/README.md
@@ -15,7 +15,7 @@ For all commercial projects, Safely must be upgraded to use a [PyUp API](https:/
 Safety can be integrated into your existing GitHub CI pipeline as an action. Just add the following as a step in your workflow YAML file after setting your `SAFETY_API_KEY` secret on GitHub under Settings -> Secrets -> Actions:
 
 ```yaml
-      - uses: pyupio/safety@2.2.0
+      - uses: pyupio/safety@2.2.1
         with:
           api-key: ${{ secrets.SAFETY_API_KEY }}
 ```
diff --git a/safety/VERSION b/safety/VERSION
@@ -1 +1 @@
-2.2.0
+2.2.1

-Original file line number
+Diff line change
 Safety can be integrated into your existing GitHub CI pipeline as an action. Just add the following as a step in your workflow YAML file after setting your `SAFETY_API_KEY` secret on GitHub under Settings -> Secrets -> Actions:
 ```yaml
 -      - uses: pyupio/[email protected].0
 +      - uses: pyupio/[email protected].1
         with:
           api-key: ${{ secrets.SAFETY_API_KEY }}
 ```