Fix bugged 2.3.0 release - safety.alerts module not included in setup.cfg

Author: cb22

CHANGELOG.md

@@ -5,6 +5,9 @@ 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.3.1] - 2022-10-05
+- Add `safety.alerts` module to setup.cfg
+
 ## [2.3.0] - 2022-10-05
 - Safety can now create GitHub PRs and Issues for vulnerabilities directly, with the new `safety alert` subcommand.
 - Support for GitHub PR and Issue alerting has been added to the GitHub Action.

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.3.0
+      - uses: pyupio/safety@2.3.1
         with:
           api-key: ${{ secrets.SAFETY_API_KEY }}
 ```

safety/VERSION

@@ -1 +1 @@
-2.3.0
+2.3.1

setup.cfg

@@ -31,7 +31,7 @@ classifiers =
 [options]
 zip_safe = False
 include_package_data = True
-packages = safety, safety.formatters
+packages = safety, safety.formatters, safety.alerts
 package_dir =
     safety = safety
 install_requires =