From f55c9271074226713b9666d8c98a5e7df10466be Mon Sep 17 00:00:00 2001 From: Yeison Vargas Date: Mon, 21 Nov 2022 16:23:17 -0500 Subject: [PATCH] Version 2.3.2 --- CHANGELOG.md | 7 +++++++ README.md | 2 +- safety/VERSION | 2 +- 3 files changed, 9 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 9bdd15cc..5c382c0b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,13 @@ 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.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. +- Fixed telemetry data missing when the CLI mode is used. +- Fixed wrong database fetching when the KEY and the database arguments are used at the same time. +- Added `SAFETY_PURE_YAML` env var, used for cases that require pure Python in the YAML parser. + ## [2.3.1] - 2022-10-05 - Add `safety.alerts` module to setup.cfg diff --git a/README.md b/README.md index 85d170ee..1b35f9ac 100644 --- 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.3.1 + - uses: pyupio/safety@2.3.2 with: api-key: ${{ secrets.SAFETY_API_KEY }} ``` diff --git a/safety/VERSION b/safety/VERSION index 3aaf1b48..f90b1afc 100644 --- a/safety/VERSION +++ b/safety/VERSION @@ -1 +1 @@ -2.3.2.dev +2.3.2