drover v0.7.2.pre1 Release Notes

Release Date: 2020-10-18 // about 1 year 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 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.


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