NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #2654 most downloaded on PyPI
A schema and validator for YAML.
Last release 10 months ago
20 Nov 2025
Ships unpredictably
gaps range from 2 weeks to 2.0 years
Some releases are documented
notes for 23 of 50 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
50 releases · first in 2014
feat: enhance MAC address validation to support Cisco dotted notation by @ChristopherJHart in #278
Full Changelog: 6.0.0...6.1.0
Adds -e PATTERN / --exclude PATTERN argument to the CLI
New Features
-e PATTERN / --exclude PATTERN argument to the CLI-n auto to spawn child processes equal to number of system CPUsBreaking Changes
Full Changelog: 5.3.0...6.0.0
One column per quarter.
Create .pre-commit-hooks.yaml by @rsrdesarrollo in #258
Full Changelog: 5.2.1...5.3.0
(fix)semver: SyntaxWarning: invalid escape sequence by @kiblik in #248
Add CodeQL workflow for GitHub code scanning by @lgtm-com in #205
Full Changelog: 5.1.0...5.2.0
fix(cli): check schema to be a valid path first by @AndreyNautilus in #241
Full Changelog: 5.0.0...5.1.0
fix 3.12 deprecations by @sigma67 in #237
Enable 'yamale -v' for version reporting.
Enable 'yamale -v' for version reporting.
Nothing published for this version
Adds new constraint options for strings.
Adds new constraint options for strings.
Nothing published for this version
The change in PR https://github.com/23andMe/Yamale/pull/173 mitigates that specific issue. We are unaware of any backwards incompatibility with the in…
This release is created to address the following issue: https://github.com/23andMe/Yamale/issues/167
The change in PR https://github.com/23andMe/Yamale/pull/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.
This release fixes a bug where a well-formed schema file can execute arbitrary code on the system running Yamale.
This release fixes a bug where a well-formed schema file can execute arbitrary code on the system running Yamale.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
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.
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.
Nothing published for this version
Note: Due to a packaging bug, users running Python 2.x should pin the major version of Yamale to 2.x.
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:
--strict command line is now replaced with --no-strict for those that want the old behavior. See the README for more details.Ability to specify schema and data without a filename #104
Ability to specify schema and data without a filename #104
Removed the printing of stacktraces to the command line (#83) Add support for a "key" constraint to the "map" validator (#95) Make any() accept anythi
Removed the printing of stacktraces to the command line (#83) Add support for a "key" constraint to the "map" validator (#95) Make any() accept anything (#93) Empty data file should fail if schema requires something (#81) Add a check for an empty schema file (#70)
Fixed a bug when using a schema with a static list and trying to validate a list with a missing element. https://github.com/23andMe/Yamale/issues/66
Fixed a bug when using a schema with a static list and trying to validate a list with a missing element. https://github.com/23andMe/Yamale/issues/66
This release brings strict mode to Yamale. With strict mode, elements defined in your YAML that aren't specified in the schema will cause a validation
This release brings strict mode to Yamale. With strict mode, elements defined in your YAML that aren't specified in the schema will cause a validation error. You can also validate dynamic keys and include validators.
We've bumped the version to 2.x due to an incompatibility. In the 1.x branch, if all the children of a node are optional, then the parent is optional as well. In the 2.x branch, the parent will no longer be optional in this case.
Nothing published for this version
Nothing published for this version
New regex validator! See README for details.
New regex validator! See README for details.
Nothing published for this version
Added none kwarg to all validators. See documentation for usage.
Added none kwarg to all validators. See documentation for usage.
Just updating setup.py so the README displays correctly in PyPI.
Just updating setup.py so the README displays correctly in PyPI.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Added the day and timestamp validators. Added min and max to the list validator. Bug fixes.
Added the day and timestamp validators.
Added min and max to the list validator.
Bug fixes.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Check out the readme, near the bottom.
Check out the readme, near the bottom.
Older versions of Python 3 may work, but only 3.4 is tested.
Added support for Python 3.4+
Older versions of Python 3 may work, but only 3.4 is tested.
Your coding agent can read these notes before it upgrades. Set up the MCP server →