drover v0.7.2.pre1 Release Notes
Release Date: 2020-10-18 // over 5 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.devtags and toward.pretags
🚀 with support from thesetuptools_scmtool 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_arnslist)
📦 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
RECORDfiles, and - Fields in source distribution
PKG-INFOfiles are sorted when hashing.
📦 Oddly,
PKG-INFOfiles from source package installations enumerate fields in a
📦 non-deterministic order; i.e. installing the same package multiple times may
✅ yield aPKG-INFOfile with fields in a different order. During testing, this
behavior was witnessed with theProvides-Extrafield. - a custom requirements layer name (via