Starting version 2.3.3.dev

pyupio · Nov 21, 2022 · e6bceee · e6bceee
1 parent f55c927
commit e6bceee
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,6 +5,8 @@ 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/)
 
+## [Unreleased] 2.3.3.dev
+
 ## [2.3.2] - 2022-11-21
 - Fixed #423: Bare output includes extra line in non-screen output with no vulnerabilities.
 - Fixed #422: ResourceWarning (unclosed socket) in safety v.2.3.1.

diff --git a/README.md b/README.md
@@ -10,6 +10,15 @@ By default it uses the open Python vulnerability database [Safety DB](https://gi
 
 For all commercial projects, Safely must be upgraded to use a [PyUp API](https://pyup.io) using the `--key` option.
 
+# Supported and Tested Python Versions
+
+Python: `3.6`, `3.7`, `3.8`, `3.9`, `3.10`, `3.11`
+
+Safety supports the above versions but only is tested in the latest patch version available at [Python for Actions
+](https://github.com/actions/python-versions/blob/main/versions-manifest.json). For instance, in Python `3.6` we only will test with `3.6.15`, which is the latest Python 3.6 version available on GitHub actions.
+
+Make sure to use the latest patch available for your Python version.
+
 # Using Safety as a GitHub Action
 
 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:

diff --git a/safety/VERSION b/safety/VERSION
@@ -1 +1 @@
-2.3.2
+2.3.3.dev