v3.0.0

What's Changed

⚠️ Potentially breaking changes ⚠️ - details

• Better gitignore support by @GrantBirki in #66

Full Changelog: v2...v3.0.0

v2.7.1

What's Changed

• fix(ajv-custom-format): tighten implemenation and provide missing tests by @cfuerst in #64

Full Changelog: v2.7.0...v2.7.1

v2.7.0

What's Changed

This release adds a new input option (ajv_custom_regexp_formats) which allows users to define custom ajv regex formats for validating JSON data through their schemas. Thanks to @cfuerst for this excellent new feature! 🎉

Usage of this new feature is documented on the main README of this Action 📚

• feat(ajv-custom-format): initial poc by @cfuerst in #61
• node package updates by @GrantBirki in #62
• add Custom Regex Formats section to the documentation by @GrantBirki in #63

New Contributors

• @cfuerst made their first contribution in #61

Full Changelog: v2.6.2...v2.7.0

v2.6.2

What's Changed

This release mostly just updates internal node dependencies used by this GitHub Action

• General Updates by @GrantBirki in #59

Full Changelog: v2.6.1...v2.6.2

v2.6.1

What's Changed

Internal node dependency updates and CI updates

• General Dependency Updates by @GrantBirki in #52

Full Changelog: v2.6.0...v2.6.1

v2.6.0

What's Changed

• support ajv strict option via inputs by @GrantBirki in #49

Full Changelog: v2.5.0...v2.6.0

v2.5.0

What's Changed

• change checkout version in the docs by @GrantBirki in #44
• use glob pattern matching for the files input by @GrantBirki in #46
• node updates by @GrantBirki in #47

Full Changelog: v2.4.0...v2.5.0

v2.4.0

What's Changed

• Feature: Allow YAML multiple documents by @bbompk in #40
• update bundle by @GrantBirki in #41
• Bump @babel/traverse from 7.22.17 to 7.23.2 by @dependabot in #42
• Updates by @GrantBirki in #43

New Contributors

• @bbompk made their first contribution in #40

Full Changelog: v2.3.1...v2.4.0

v2.3.1

What's Changed

• upgrade to node20 by @GrantBirki in #35

Full Changelog: v2.3.0...v2.3.1

v2.3.0

v2.3.0

This release adds a new Action's input that allows users to configure the "version" of the JSON schema definition they wish to use with the JSON schema validator.

New Option: json_schema_version

Acceptable Values:

• "draft-07" default - this is used if you leave it blank
• "draft-2019-09"
• "draft-2020-12"

What's Changed

• Support More JSON Schema Versions by @GrantBirki in #34

Full Changelog: v2.2.1...v2.3.0