v0.7.2.pre1

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 the setuptools_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.

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 a PKG-INFO file with fields in a different order. During testing, this
behavior was witnessed with the Provides-Extra field.

v0.7.1.dev2

v0.7.1.dev2 Release Notes

Summary

• Add finer-grained SHA256 hashing (see below for impacts); improve log/interactive output control
• Interactive console sessions now properly synchronize progress bar updates
• Enable support for Python 3.6 and 3.7

Hashing impacts

Drover's new hashing approach is not backwards-compatible; hashes
generated with this release will not collide with older releases even if
no package content has changed. This hash incompatibility will only
result in at most one extraneous round of uploading during your next
deploy.

The new hashing approach leverages SHA256 hashes and pre-computed hashes
for most Python package files via wheel RECORD files when applicable.

Interactive output and verbosity improvements

Log verbosity can now either be increased with cumulative -v arguments
or squelched with the -q argument.

Drover now automatically detects support for interactive terminal output
and allows manually overriding this behavior via the mutually-exclusive
--interactive and --non-interactive arguments.

v0.7.1.dev1

v0.7.1.dev1 Release Notes

This pre-release extends interface documentation and unit test coverage.

v0.7.0

v0.7.0 Release Notes

This is the first release of drover, a command-line interface utility to efficiently publish and update a Lambda function and requirements layer representation of a Python package directory.

This release mirrors the drover 0.7.0 release on PyPI.