Skip to content

Releases: serverless/serverless-python-requirements

6.1.1 (2024-06-03)

13 Aug 17:29
57f7c6b
Compare
Choose a tag to compare

6.1.0 (2024-03-27)

27 Mar 23:35
Compare
Choose a tag to compare

Features

Bug Fixes


Comparison since last release

6.0.0 (2022-10-23)

25 Oct 20:08
Compare
Choose a tag to compare

⚠ BREAKING CHANGES

  • Changes default dockerImage used for building dependencies (now uses images from public.ecr.aws/sam repository)
  • Requires pipenv in version 2022-04-08 or higher

Features

Bug Fixes

Maintenance Improvements


Comparison since last release

5.4.0 (2022-03-14)

15 Mar 14:35
Compare
Choose a tag to compare

Features

Maintenance Improvements


Comparison since last release

5.3.1 (2022-01-28)

28 Jan 16:04
Compare
Choose a tag to compare

Bug Fixes


Comparison since last release

5.2.2 (2021-12-03)

03 Dec 14:19
Compare
Choose a tag to compare

Bug Fixes


Comparison since last release

5.2.1 (2021-11-30)

02 Dec 11:35
Compare
Choose a tag to compare

Maintenance Improvements

Changelog

All notable changes to this project will be documented in this file. See standard-version for commit guidelines.


Comparison since last release

Version 5.2.0

18 Nov 15:45
Compare
Choose a tag to compare
  • feat: Introduce schema validation for module property (#641) @rileypriddle
  • fix: Ignore functions defined with image @pgrzesik
  • fix: Fix help output for requirements container command @medikoo
  • chore: Register serverless as peer dependency @medikoo
  • test: Pin dependencies to avoid unexpected upgrades @pgrzesik

Version 5.1.1

01 Apr 22:01
Compare
Choose a tag to compare

Changes:

  • Fixes to CI/CD
  • Fixes to Poetry support
  • Documentation cleanup
  • Update linting
  • Update dependencies

Version 5.1.0

22 Feb 17:08
Compare
Choose a tag to compare

Changes:

  • Removes compatibility with pre-release poetry. (Minor version bump.)
  • Bump werkzeug version to address security issue.
  • Correct word splitting on pip commands.
  • circle CI is working again; much thanks to @miketheman

Known risks:

  • Windows CI is still down