drover v0.7.2.pre1 Release Notes
Release Date: 2020-10-18 // almost 4 years ago-
๐ Release v0.7.2.pre1
๐ Notable Fixes:
- โก๏ธ Ensure first update includes requirements layer
- ๐ฒ Correct log output to show newest (not prior) requirements layers
Housekeeping:
๐ Migrate CI/CD prerelease process away from.dev
tags and toward.pre
tags
๐ with support from thesetuptools_scm
tool to ensure public release tags are
compatible with semantic versioning.๐ Changes:
- ๐ป 651a72b Add exception chaining for Drover class errors
- ๐ f23eed7 Move CI/CD to Azure Pipelines; version from tags
- โก๏ธ 6b06bfd Ensure first update includes requirements layer
- ๐ dec0f9e Add initial Sphinx documentation
๐ This list of changes was auto generated.
Previous changes from v0.7.1
-
๐ v0.7.1 Release Notes
The settings file now allows specifying:
- a custom requirements layer name (via
requirements_layer_name
), and - custom supplemental layer ARNs (via the
supplemental_layer_arns
list)
๐ฆ Python package hash generation is now more resilient; to ensure
๐ฆ reasonably-similar package installations yield the same hash:- ๐ฆ Package-relative file names are used when hashing Wheel
RECORD
files, and - Fields in source distribution
PKG-INFO
files are sorted when hashing.
๐ฆ Oddly,
PKG-INFO
files from source package installations enumerate fields in a
๐ฆ non-deterministic order; i.e. installing the same package multiple times may
โ yield aPKG-INFO
file with fields in a different order. During testing, this
behavior was witnessed with theProvides-Extra
field. - a custom requirements layer name (via