jsonschema_rs 0.58.2-aarch64-linux → 0.58.4-aarch64-linux

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 69b819cc2fe64d0e7448f045c79b0cc62390effb79682f2ad12c3a8a3b2a7bd4
4
- data.tar.gz: ac9863ea8587e886ea270cd3ca8d5f145462da067aa8652707fb5ab1c44d6331
3
+ metadata.gz: f3dacad360e9130c73e19975a344c8b385106a5d11d8196c0cd32fdc7fdbc094
4
+ data.tar.gz: 0c20d173684c3c7f196359d00ec0e804c103fc8b722682dc0521ef8d264a3086
5
5
  SHA512:
6
- metadata.gz: 1b8c24c08dfeb6dc1fdae9832eb359ec8e72de2a0a85a094b9c0f9447446932cd629455b38498dfc2b734adca047535229005d2fe5275b86548b505efa920677
7
- data.tar.gz: 5dcb14b03718d029ff981f63029a723bf5eb56dd78ede123179884b476b60d1469a5833ed1cc0b17b9afdb32f7bbd6a672a3912f2d0f6f1d3d06626a204115a0
6
+ metadata.gz: 332d4cea68514ea3ad83ccbc8e40f00f470f48f46650bb735681071cc5bdc25fc88bfa62efebf21b9794fa01aafa33fdb3372dcfa401a633b54f69ad3dde5226
7
+ data.tar.gz: 3388846cb78a68de318d076c2caf2b3addeb7a56380c420a04d693eb60603e82e47784193c44225331fc6efdfc8a128ea07d93873659ee8b9a4bea0fdbd896da
data/CHANGELOG.md CHANGED
@@ -2,6 +2,40 @@
2
2
 
3
3
  ## [Unreleased]
4
4
 
5
+ ## [0.58.4] - 2026-10-01
6
+
7
+ ### Fixed
8
+
9
+ - `inspect` of a `validator_for` validator naming the default draft instead of the one `$schema` declares.
10
+ - `unevaluatedProperties` and `unevaluatedItems` beside a `$recursiveRef` ignoring what the reference target evaluates.
11
+ - `unevaluatedProperties` ignoring the configured regex engine and its limits for `patternProperties`.
12
+ - Absolute keyword location and `schemaLocation` of keywords a `$ref` JSON Pointer reaches through a subschema with its own `$id`.
13
+ - `type`, `minItems` and `maxItems` ignored beside `items` when the applicator vocabulary is disabled.
14
+ - Absolute keyword location and `schemaLocation` of keywords inside a nested `$id` resource counting from the document root.
15
+ - `required` beside `properties` ignored when the applicator vocabulary is disabled, and `required`, `minContains` and `maxContains` applied when the validation vocabulary is disabled.
16
+ - Absolute keyword location and evaluation output of `type` errors in a `type`-only `items` subschema pointing at `items` instead of the failing element's `type`.
17
+ - Absolute keyword location of `patternProperties` annotations missing its JSON Pointer fragment.
18
+ - Evaluation output of `type: array` beside schema-form `items` omitting passing `type`, `minItems` and `maxItems` units and nesting failing ones under `items`.
19
+ - Evaluation output `schemaLocation` and absolute keyword location of `$ref`, `$dynamicRef` and `$recursiveRef` nodes not pointing at the reference target.
20
+ - Evaluation output `schemaLocation` URIs not percent-encoding their fragment, such as a space in a property name.
21
+ - Absolute keyword location of errors and annotations from a whole subschema, such as `false`, missing its JSON Pointer fragment.
22
+ - Absolute keyword location of `required`, `minContains` and `maxContains` errors pointing at a sibling keyword.
23
+ - Evaluation annotations from `$ref` siblings in Draft 4, 6 and 7 schemas.
24
+ - Masked `additionalItems` messages counting allowed items instead of extra ones, and "1 items" in masked `unevaluatedItems` messages.
25
+ - `$dynamicRef` and `$recursiveRef` resolving in the dynamic scope of another path to the same schema, depending on property order.
26
+ - `unevaluatedProperties` and `unevaluatedItems` ignoring what `then` or `else` evaluates when `if` is `true` or `false`.
27
+ - Stack overflow when building validators for long `$ref` chains.
28
+ - `format: "regex"` and meta-schema validation rejecting escaped punctuation such as `\-` in patterns.
29
+ - Build errors for an invalid `patternProperties` regex reporting the subschema instead of the pattern and its location.
30
+
31
+ ## [0.58.3] - 2026-09-30
32
+
33
+ ### Fixed
34
+
35
+ - Keywords of a subschema declaring a Draft 2019-09+ `$schema` under a Draft 4, 6 or 7 root being ignored.
36
+ - Evaluation annotations including those from subschemas of a failing schema (a failing schema produces no annotations).
37
+ - Embedded resources declaring their own `$schema` being checked against the root's meta-schema.
38
+
5
39
  ## [0.58.2] - 2026-09-28
6
40
 
7
41
  ### Fixed
@@ -603,7 +637,9 @@
603
637
 
604
638
  - Initial public release
605
639
 
606
- [Unreleased]: https://github.com/Stranger6667/jsonschema/compare/ruby-v0.58.2...HEAD
640
+ [Unreleased]: https://github.com/Stranger6667/jsonschema/compare/ruby-v0.58.4...HEAD
641
+ [0.58.4]: https://github.com/Stranger6667/jsonschema/compare/ruby-v0.58.3...ruby-v0.58.4
642
+ [0.58.3]: https://github.com/Stranger6667/jsonschema/compare/ruby-v0.58.2...ruby-v0.58.3
607
643
  [0.58.2]: https://github.com/Stranger6667/jsonschema/compare/ruby-v0.58.1...ruby-v0.58.2
608
644
  [0.58.1]: https://github.com/Stranger6667/jsonschema/compare/ruby-v0.58.0...ruby-v0.58.1
609
645
  [0.58.0]: https://github.com/Stranger6667/jsonschema/compare/ruby-v0.57.0...ruby-v0.58.0
Binary file
Binary file
Binary file
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module JSONSchema
4
- VERSION = "0.58.2"
4
+ VERSION = "0.58.4"
5
5
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: jsonschema_rs
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.58.2
4
+ version: 0.58.4
5
5
  platform: aarch64-linux
6
6
  authors:
7
7
  - Dmitry Dygalo
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2026-09-28 00:00:00.000000000 Z
11
+ date: 2026-10-01 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bigdecimal