Use conventional-commits repo for CI checks

Contents

Operations

• Use conventional-commits repo for CI checks

Use LAST_RELEASE mode when compiling release notes

Contents

Operations

• Use LAST_RELEASE mode when compiling release notes

Add missing mkver.conf

Contents

Operations

• Add missing mkver.conf

Enable continuous deployment with semantic versions

Contents

Operations

• Run release workflow on merge of any branch into main
• Add Conventional Commits pre-commit hook
• Replace check-version-consistency job with check-semantic-version job, which checks that the version in setup.py is the same as the semantic version expected by git-mkver given the Conventional Commits since the last tag
• Add the update-pull-request workflow that auto-generates part of the PR description on each commit
• Run publish test job on all branches and make it dependent on check-semantic-version job passing
• Rename tests job to run-tests

Release/0.0.20

Contents

New Features

• Add file tags template to twine schema
• Add file tags template validation for datasets

Breaking changes

• Require datasets to be inside "datasets" field in "manifest" fields of twine.json
• Make tags an object and add labels field to manifest schema
• Separate old tags in examples and tests into labels and new tags

Minor improvements

• Update tags format in examples in docs
• Remove filters field from manifest in twine schema
• Remove kind field from manifest schema (i.e. "multi-dataset")
• Factor out manifest schema into definition in twine schema and use for all three manifest types
• Split getting schema from validating against schema in Twine

Fixes

• Add missing configuration_manifest to twine schema
• Fix name of configuration_values_schema in twine schema and twine.json files

Testing

• Use correct method in manifest validation test
• Update tags format

Release/0.0.19

Contents

Fixes

• Allow usage with python>=3.6

Release/0.0.18

Contents

Breaking changes

• Change tags serialisation to a sorted list of strings

Operations

• Improve description of release workflow

Release/0.0.17

Contents

Breaking changes

• Disallow default values for credentials
• Disallow extra fields in credentials strand of twine.json
• Return set of names of validated credentials from Twine.validate_credentials (not their values)

Fixes

• Add *args and **kwargs to Twine.validate_credentials to ignore extra arguments from Twine.validate (this was causing errors)
• Fix skip CI tests flag

Minor improvements

• Use latest versions of flake8, isort, and black in pre-commit and apply to all files retrospectively

Testing

• Stop CI testing for python <= 3.7
• Start CI testing on Windows and MacOS (and continue with Ubuntu)

Operations

• Add automatic release workflow

Make children credentials more flexible; fix CI check and allow test skipping

Contents

Features

• Allow skipping of CI tests if #skip_ci_tests is in the commit body - the use case is to reduce unnecessary computation when knowing the tests will fail for a commit but still wanting to commit.

Breaking changes

• Require environment variable for children credentials (#67) - note this was accidentally merged into main just before this release branch rather than into this release branch

Minor fixes and improvements

• Close #65 - ensure version consistency GitHub check doesn't fail on main (or any one-word) branch

Quality Checklist

• New features are fully tested (No matter how much Coverage Karma you have)

Fix child and missing strand validation; add backend field to chidren

Contents

New features

• Replace uri_env_name field with new backend field in children schema that provides children using Google Pub/Sub with the configurations to communicate

Minor improvements and fixes

• Add version consistency GitHub action
• Fix child validation by adding missing argument source
• Fix missing strand data validation by making strand attributes public (this removes the disparity between the attributes being private but the related names being used not including a leading underscore)