Releases: ehn-dcc-development/hcert-kotlin
Release 1.5.0
Changelog:
- Update dependencies:
- Common: Kotlin 1.7.10, Datetime 0.4.0, Napier 2.6.1, Gradle 7.5.1
- JVM: Zxing 3.5.0, Bouncycastle 1.70, JSON Schema validator 0.36
- JS: pki.js 2.4.0, cbor 8.1.0, ajv (JSON Schema validator) 8.11.0, QR Code 3.3.0, Bignumber 9.1.0
We can make no guarantees about the correctness of the implementation, so please do not use it without extensive testing for production use.
Release 1.4.1
Changelog:
- Import ehn-dcc-schema version 1.3.1 and 1.3.2
We can make no guarantees about the correctness of the implementation, so please do not use it without extensive testing for production use.
Release 1.4.0
Changelog:
- Add second respository for trust anchors to verify AT-specific vaccination exemptions (prefix AT1:) against (see
buildVerificationChain
) - Fix constructors and overloads for Java callers
- Introduce a debug verification chain
- Introduce possibility to anonymise personal data (JVM only)
- Update dependencies:
- Common: Kotlin: 1.5.31, kotlinx.serialization: 1.3.0, kotlinx.datetime: 0.3.0, Kotest: 4.6.3, Napier (Logging): 2.1.0
- JVM: Bouncy Castle: 1.69, Json Schema Validation Lib: 2.1.0
- JS: pako (ZLib): 2.0.4, pkijs: 2.1.97, util: 0.12.4, cbor: 8.0.2, node-inspect-extracted: 1.0.8, ajv (JSON schema validator): 8.6.3, ajv-formats: 2.1.1
- JS:
- Switch to upstream cose-js 0.7.0 (deprecates forked version)
- Fix deprecated calls to
Buffer
constructor (possibly not all calls yet) - Switch intermediate (=node) output from CommonJS to UMD
- Experimental NodeJS support
- Enable outputting a bundled js module (UMD) targeting NodeJS if desired
- the Gradle npm-publish plugin does not work as desired
We can make no guarantees about the correctness of the implementation, so please do not use it without extensive testing for production use.
Release 1.3.2
Changelog:
- Export
SignedDataDownloader
to JS
We can make no guarantees about the correctness of the implementation, so please do not use it without extensive testing for production use.
Release 1.3.1
Changelog:
- Rework verification of timestamps in the HCERT CWT, to work around some weird codes appearing in production
- New error codes
CWT_NOT_YET_VALID
andPUBLIC_KEY_NOT_YET_VALID
We can make no guarantees about the correctness of the implementation, so please do not use it without extensive testing for production use.
Release 1.3.0
Changelog:
- Parse a missing
dr
value in HCERT Test entries correctly - Add class
SignedData
to holdcontent
andsignature
of a TrustList - Add services to encode and decode Business Rules (also called Validation Rules)
- Add services to encode and decode Vaule Sets
We can make no guarantees about the correctness of the implementation, so please do not use it without extensive testing for production use.
Release 1.2.0
Changelog:
- Split faulty implementations, sample data, to separate artifact:
ehn.techiop.hcert:hcert-kotlin-jvmdatagen
- Add option to get a data class with "nice" names when validating in JS (equivalent to JVM)
- API change: GreenCertificate now uses arrays for test/vaccination/recovery
- Add
certificateSubjectCountry
toVerificationResult
, to get the country of the HCERT's signature certificate - Relax schema validation once more to allow explicit
null
values fornm
,ma
in HCERT Test entries
We can make no guarantees about the correctness of the implementation, so please do not use it without extensive testing for production use.
Release 1.1.2
Release 1.1.1
Changelog:
- Changes the
tc
(testing facility) in HCERT Test entries to optional, i.e. nullable String
We can make no guarantees about the correctness of the implementation, so please do not use it without extensive testing for production use.
Release 1.1.0
This release aims at being able to verify as many QR codes out there as possible. It is tested against https://github.com/eu-digital-green-certificates/dgc-testdata/ and contains several work arounds for known issues of QR codes already issued, e.g. datetime formatting issues.
Changelog:
- Try to parse as many dates and datetimes as possible
- Perform a very relaxed schema validation by default
- Add errors for trust list loading
- Support lower Android targets by not using java.util.Base64
- Publish library on jitpack.io
We can make no guarantees about the correctness of the implementation, so please do not use it without extensive testing for production use.