Repository navigation
Releases
5.8.11
What's Changed
Full Changelog: 5.8.10...5.8.11
5.8.10
What's Changed
Full Changelog: 5.8.9...5.8.10
JSON::Schema::Corvus 0.1.2
- A leap second is a valid date-time only on a day that ended with one. date-time accepted 23:59:60 UTC on any
day; it now accepts a leap second only on the 27 days the IERS ended with one, from 1972-06-30 to 2016-12-31, in
whatever offset it is written (1998-12-31T15:59:60-08:00 is valid, 1999-12-31T23:59:60Z is not). time is
unchanged: it has no date, so it accepts a leap second whenever the time is 23:59 in UTC. JSON::Schema::Corvus::XS
does the same from v0.1.1. The JSON-Schema-Test-Suite's leap-second cases, which the suite test skipped, now run
and pass.
corvus-json-schema for Object Pascal 0.1.3
The Corvus JSON Schema evaluator for Object Pascal, version 0.1.3: the source of the package
(src-pas/corvus-json-schema), as a .zip and as a .tar.gz. See its README.md for how to use it.
V0.1.3 fixes leap seconds in the date-time format. date-time accepts a leap second (23:59:60 UTC) only on the 27 days that the IERS has ended with one, from 1972-06-30 to 2016-12-31, in whatever offset the value is written (1998-12-31T15:59:60-08:00 is valid, 1999-12-31T23:59:60Z is not). It accepted 23:59:60 UTC on any day. time is unchanged: it has no date, so it accepts a leap second whenever the time is 23:59 in UTC. The .NET engine does the same from V5.8.6, the Rust crate from 0.2.2, the Go module and the Java library from 0.1.5, the Julia package from 0.1.4 and the OCaml package from 0.1.3. The JSON-Schema-Test-Suite's leap-second cases, which the suite run skipped, now run and pass. There are no API changes.
5.8.8
What's Changed
- Rust crate 0.2.2: a leap second is a valid date-time only on a day that ended with one, with the C library and the Ruby, PHP and Python packages by @mwadams in #1064
- R 0.1.4, Alien::CorvusJsonSchema v0.1.2 and JSON::Schema::Corvus::XS v0.1.1: leap seconds on the IERS days, from crate 0.2.2 and C library 0.1.7 by @mwadams in #1065
- V5.8.8: pattern gives the right answer under native AOT, and every build checks its AOT profile by @mwadams in #1066
Full Changelog: 5.8.7...5.8.8
JSON::Schema::Corvus::XS 0.1.1
- Built with Alien::CorvusJsonSchema v0.1.2, on C library 0.1.7 or later: a leap second is a valid date-time
only on the 27 days that ended with one (23:59:60 UTC). The test suite runs the JSON-Schema-Test-Suite's
leap-second cases, which it skipped.
Alien::CorvusJsonSchema 0.1.2
- Installs the release package of C library 0.1.7, and needs an installed library to be 0.1.7 or later. 0.1.7
accepts a leap second in a date-time only on the 27 days that ended with one (23:59:60 UTC), so
JSON::Schema::Corvus::XS gets that when it is built.
corvus-json-schema C library 0.1.7
The corvus-json-schema C library and its C++ wrapper, version 0.1.7: headers, shared and static libraries, a CMake package and a pkg-config file for each platform, and CorvusJsonSchema.xcframework.zip (static libraries for macOS, iOS and the iOS simulator, for a Swift package's binaryTarget; SwiftPM checksum 4e776c94411b20e6d51667e64a2cb38a2d3e4c1b2f6cb4779feae18f668f7f62). See src-rs/corvus-json-schema-capi/VERSIONHISTORY.md and DESIGN.md.
5.8.7
What's Changed
- V5.8.7: publish from a job of build.yml again, so NuGet.org accepts the Trusted Publishing token by @mwadams in #1063
Full Changelog: 5.8.6...5.8.7
5.8.6
What's Changed
- Build infrastructure: ZeroFailed 2.0 with Trusted Publishing through the shared pipeline, and setup-fortran 1.11.0 by @mwadams in #1060
- V5.8.6: leap seconds are valid date-times on the days that ended with one, and time offsets take any hour RFC 3339 allows by @mwadams in #1062
Full Changelog: 5.8.5...5.8.6