summaryrefslogtreecommitdiff
path: root/CHANGELOG.rst
Commit message (Collapse)AuthorAgeFilesLines
* Re-enable (but deprecate) automatic reference retrieval.Julian Berman2023-04-251-0/+4
| | | | | | | | | | | | | Changing this without deprecation is backwards incompatible, so we re-introduce a warning. This only applies if you have not configured neither a Registry nor a legacy RefResolver. Both of the former 2 cases already have 'correct' behavior (the former will not automatically retrieve references and is not backwards incompatible as it is a new API, and the latter will do so but is already fully deprecated by this release). Cloess: #1089
* Add a few more lines to the CHANGELOG.Julian Berman2023-03-281-0/+2
|
* Add 2 more minor deprecations to the changelog.v4.18.0a1Julian Berman2023-03-151-0/+11
|
* Ignore additionalItems when items isn't present on 2019.Julian Berman2023-03-141-0/+1
| | | | This is specified behavior, see json-schema-org/JSON-Schema-Test-Suite#643.
* Mention 3.7 support being dropped in the CHANGELOG.Julian Berman2023-03-141-1/+5
| | | | And elaborate even further on the ref change.
* Deprecate jsonschema.RefResolver from both places it is importable.Julian Berman2023-02-211-0/+7
| | | | | | Internal uses of it will be removed, replaced with referencing's resolution APIs, though RefResolver will continue to function during its deprecation period.
* Fix instantiating validators with cached refs-to-bool schemas.v4.17.3Julian Berman2022-11-291-0/+6
| | | | Closes: #1018
* Durations without trailing units aren't valid durations.Julian Berman2022-11-281-0/+9
| | | | Refs: json-schema-org/JSON-Schema-Test-Suite#606
* v4.17.1 -> CHANGELOGv4.17.1Julian Berman2022-11-221-0/+6
|
* Enable format validation by default in check_schema.v4.17.0Julian Berman2022-11-011-0/+5
| | | | | | | | This catches some additional schema problems (ones caught by format validation in the metaschema, which was previously treated as annotation-only in check_schema). Closes: #904
* Deprecate the CLI (via import or running normally).Julian Berman2022-11-011-0/+8
| | | | | | | | | | It is less featureful (and less maintained) than the new 'official' option, check-jsonschema. See https://github.com/python-jsonschema/check-jsonschema for details. Closes: #600
* Fix the grammar on ErrorTree's repr when it has 1 error.Julian Berman2022-10-051-0/+5
|
* Deprecate jsonschema.draftN_format_checker attributes.v4.16.0Julian Berman2022-09-091-0/+4
| | | | | | | | | | | | | | | | Format support / enablement will change with vocabulary support, but in the interim, now that #905 is merged, these objects are better accessed by retrieving them directly from the corresponding validator. In other words: don't do: from jsonschema import draft202012_format_checker just do from jsonschema import Draft202012Validator do_whatever_with(Draft202012Validator.FORMAT_CHECKER)
* v4.16.0 -> CHANGELOGJulian Berman2022-09-091-0/+6
|
* Add a note to the CHANGELOG about #988.Julian Berman2022-08-301-0/+1
|
* Add a note to the CHANGELOG about the minor ref change.Julian Berman2022-08-281-0/+8
|
* Add a note to the CHANGELOG about the typing tweaks.v4.14.0Julian Berman2022-08-211-0/+1
|
* Fix unevaluatedItems on draft2019.Julian Berman2022-08-201-2/+2
| | | | | | | | This was trivial, other than needing to copy paste the function which anyhow needs removal. It only didn't work previously because of the items -> prefixItems rename in draft2020.
* We've wontfixed the upstream issue.Julian Berman2022-08-201-0/+2
|
* Deprecate FormatChecker.cls_checks.Julian Berman2022-08-201-0/+6
| | | | | | It exposes fragile global state. Closes: #519.
* Support validator classes whose metaschema uses a different dialect.v4.13.0Julian Berman2022-08-191-0/+10
| | | | | | | | | | | In other words, one may author validator classes (via jsonschema.validators.create or extend) whose meta schema defines schema behavior using JSON Schema draft2020-12 but whose schemas are in its own dialect. Said again differently, the set of valid schemas for a validator class may be governed by one draft, while the schema behavior itself is governed by another.
* Update the CHANGELOG.v4.12.1Julian Berman2022-08-181-0/+15
|
* Fix the rest of the CHANGELOG headings from #983.v4.11.0Julian Berman2022-08-181-3/+8
|
* Merge pull request #983 from hynek/fancy-sparklesJulian Berman2022-08-181-47/+47
|\ | | | | jsonschema deserves a ✨fancy✨ readme
| * Change version header markersHynek Schlawack2022-08-181-47/+47
| |
* | Use an explicit default provided to validator_for in all cases.v4.10.3Julian Berman2022-08-181-0/+6
| | | | | | | | | | | | | | | | Previously it was only used when $schema was not present, but clearly it should be used even when it is but the URI is not recognized. Combined with #981 this *hopefully* now handles the remaining downstream users with subclasses.
* | Fix one more Validator.evolve issue for downstream Validators.v4.10.2Julian Berman2022-08-171-0/+5
| | | | | | | | | | | | Here for renamed attributes out of attrs-using classes. Refs: 'https://github.com/python-jsonschema/jsonschema/issues/982#issuecomment-1218117191'
* | Fix calling Validator.evolve for some downstream users.v4.10.1Julian Berman2022-08-171-0/+11
|/ | | | | | | | | | | | | | The broken case here was subclassing a validator class, something that isn't really a supported use of the Validator classes, but of course one can't blame anyone too much since doing so didn't raise an error or emit any warning. In the next release subclassing will warn, and at some point afterwards will become an explicit error. If you're a downstream user of this library looking for a way to avoid whichever inheritance is currently needed in your library feel free to reach out and I'll try to help. Closes: #982
* Add support for referencing schemas across different drafts.Julian Berman2022-08-161-0/+6
| | | | | | | | In other words, a draft 7 schema may reference a draft 2019 schema (or vice versa), and now correctly apply the 2019 rules within the referenced schema. Refs: json-schema-org/JSON-Schema-Test-Suite#587
* v4.9.1 -> CHANGELOGv4.9.1Julian Berman2022-08-031-0/+6
|
* Add the URN fix to the CHANGELOG.v4.9.0Julian Berman2022-07-311-0/+2
|
* Add a mention to the CHANGELOG.Julian Berman2022-07-291-0/+11
|
* v4.8.0 -> CHANGELOGv4.8.0Julian Berman2022-07-281-0/+7
|
* Fix best_match's `type` matching when it's an array.v4.7.2Julian Berman2022-07-121-0/+6
| | | | Closes: #973
* Minor case correction for PyPI links.v4.7.1Julian Berman2022-07-111-0/+5
|
* Enhance best match to prefer errors from matching types.Julian Berman2022-07-101-0/+6
| | | | Closes: #728
* v4.6.2 -> CHANGELOGv4.6.2Julian Berman2022-07-071-0/+5
|
* v4.6.1 -> CHANGELOGv4.6.1Julian Berman2022-06-281-0/+6
|
* v4.6.0 -> CHANGELOGv4.6.0Julian Berman2022-06-011-0/+9
|
* Add v4.5.1 to changelogStephen Rosen2022-05-271-0/+6
| | | | resolves #955
* Revert "Extend dynamicRef keyword"v4.5.1Julian Berman2022-05-051-1/+0
| | | | | | It needs performance optimization. See python-jsonschema/jsonschema#941. This reverts commit 12c791ee81baf27e54d18baf95b975bd48387dc6.
* v4.5.0 -> CHANGELOGv4.5.0Julian Berman2022-05-051-0/+10
|
* v4.4.0 -> CHANGELOGv4.4.0Julian Berman2022-01-121-0/+6
|
* v4.3.3 -> CHANGELOGJulian Berman2022-01-011-0/+5
|
* Add v4.3.2 to the changelog.Julian Berman2021-12-201-0/+5
|
* v4.3.1 -> CHANGELOGv4.3.1Julian Berman2021-12-161-1/+5
|
* docs: Update changelogDmitry Dygalo2021-12-161-3/+1
|
* perf: Replace the `Validator.evolve` method with an equivalent class attributeDmitry Dygalo2021-12-161-0/+1
|
* perf: Use cached lookups for resolving fragments if the referent document is ↵Dmitry Dygalo2021-12-161-0/+1
| | | | known
* perf: Cache reference lookups for subschemasDmitry Dygalo2021-12-151-0/+1
|
View Lorry Controller Status