5.2.1

What's Changed

• (fix)semver: SyntaxWarning: invalid escape sequence by @kiblik in #248

New Contributors

• @kiblik made their first contribution in #248

Full Changelog: 5.2.0...5.2.1

5.2.0

What's Changed

• Add CodeQL workflow for GitHub code scanning by @lgtm-com in #205
• Add ruff gh action by @cblakkan in #244
• #236 Hard fail on undefined includes by @cblakkan in #247
• Add semantic versioning (semver.org) validator by @thiagowfx in #246

New Contributors

• @lgtm-com made their first contribution in #205
• @thiagowfx made their first contribution in #246

Full Changelog: 5.1.0...5.2.0

5.1.0

What's Changed

• fix(cli): check schema to be a valid path first by @AndreyNautilus in #241
• Ruff format codebase by @cblakkan in #243

New Contributors

• @AndreyNautilus made their first contribution in #241

Full Changelog: 5.0.0...5.1.0

5.0.0

Supported python versions are now >= 3.8

What's Changed

• fix 3.12 deprecations by @sigma67 in #237
• Prep for 5.0.0; Run tests on 3.8, 3.12 by @cblakkan in #240

New Contributors

• @sigma67 made their first contribution in #237
• @cblakkan made their first contribution in #240

Full Changelog: 4.0.4...5.0.0

4.0.4

Enable 'yamale -v' for version reporting.

4.0.2

Adds new constraint options for strings.

4.0.0

This release is created to address the following issue: #167

The change in PR #173 mitigates that specific issue. We are unaware of any backwards incompatibility with the introduction of this fix, but we wanted to increment the major version number in case there are users with more complex schemas than what we test again.

We've also included the following warning in our README:

⚠️ Ensure that your schema definitions come from internal or trusted sources. Yamale does not protect against intentionally malicious schemas.

3.0.8

This release fixes a bug where a well-formed schema file can execute arbitrary code on the system running Yamale.

3.0.2

Fixes #119, strict mode was not the default on the command line....but it was for the API. This fix ensures strict mode is the default in all uses.

3.0.0

Note: Due to a packaging bug, users running Python 2.x should pin the major version of Yamale to 2.x.

We're doing a major version jump to include the following changes:

• Remove Python 2.x support
• Make the default validation "strict". The --strict command line is now replaced with --no-strict for those that want the old behavior. See the README for more details.
• Prevent int and num validators from accepting bool values. #109