Releases: zigbee-alliance/distributed-compliance-ledger
Releases · zigbee-alliance/distributed-compliance-ledger
Pre Release v1.4.0-dev3
- Update cosmos-sdk to v0.47.8
- Update golang to 1.20
Pre Release v1.4.0-dev2
- Update cosmos-sdk to v0.47.8
- Update golang to 1.20
Pre Release v1.4.0-dev1
- Support for forward and backward compatibility in DCL schemes
- Enhancements to Adding, Revoking, and Removing Non-Root Certificates
- Enable adding/revocation of NOC certificates
- Add SchemaVersion field into PKI, Compliance, Model and VendorInfo schemas
- Add commissioner remote UI flow url field into model schema
- Publish CRL Signer Certificates delegated PAA/PAI certificates
Pre Release v1.3.0-dev2
What's Changed
- Support for forward and backward compatibility in DCL schemes
- Enhancements to Adding, Revoking, and Removing Non-Root Certificates
- Enable adding/revocation of NOC certificates
- Add SchemaVersion field into PKI, Compliance, Model and VendorInfo schemas
- Add commissioner remote UI flow url field into model schema
- Publish CRL Signer Certificates delegated PAA/PAI certificates
Pre Release 1.3.0-dev1
#519 Query PAA certificates with subjectKeyId
Enable querying certs with subjectKeyId
Add migration flow (from 2 to 3 version of pki
module)
Release 1.2.2
Changes and Fixes (comparing to 0.12.0)
- Update DCL Code for Approval count to ceiling instead of round #409
- Feature: re-vote for pending #412
- Feature: remove a proposal by the owner #287
- Do not allow proposing Root certificate by non-Trustee #427
- Deletion of Model Versions #421
- Document subscribing to events via Tendermint WebSockets #414
- Adding a Model requires "partNumber" and "productLabel" but those attributes should be optional #429
- NFR: New Role with permission to add/update Vendor Info #430
- Edit of DCL Compliance entry #464
- Deletion of DCL Compliance entry #465
- Set OTA for existing Model #466
- DA PKI Revocation of PAI and VID-scoped PAA by Vendor #459
- DA PKI Revocation of non-VID scoped PAAs by Vendor #479
- Add a VID field for non-VID scoped PAAs (Root certificates) #477
- A transaction for assigning a VID to non-VID scoped PAAs (root certificates) #478
- Fix verification of certificates #503
Upgrade procedure
- The release must be applied via cosmovisor and Upgrade Proposal transactions, see pool-upgrade-how-to.md.
- The upgrade name must be equal to
v1.2
. - The release must be applied to all nodes (Validators, Observers, Sentries, etc.)
- All upgraded nodes must be at 0.12.0 or 0.12.1 with cosmovisor enabled.
- It's recommended to enable the auto-download for cosmovisor on all nodes, see pool-upgrade-how-to.md.
- Adding new nodes to the running pool (Test Net in particular) must be done via one of the ways described in running-node-in-existing-network.md.
Pre-Release 1.2.2
v1.2.2-pre Merge branch 'master' into update-docs-catchup
Release 0.12.1
Note
This release must be used instead of 0.12.0 when adding a new node to the Main Net form block 0 (see https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/docs/advanced/running-node-in-existing-network.md#3-catchup-from-genesis)
What's Changed
- Validations fix for certification dates by @DenisRybas in #505 (see #503)
Pre-Release 1.2.1
Changes and Fixes (comparing to 0.12.0)
- Update DCL Code for Approval count to ceiling instead of round #409
- Feature: re-vote for pending #412
- Feature: remove a proposal by the owner #287
- Do not allow proposing Root certificate by non-Trustee #427
- Deletion of Model Versions #421
- Document subscribing to events via Tendermint WebSockets #414
- Adding a Model requires "partNumber" and "productLabel" but those attributes should be optional #429
- NFR: New Role with permission to add/update Vendor Info #430
- Edit of DCL Compliance entry #464
- Deletion of DCL Compliance entry #465
- Set OTA for existing Model #466
- DA PKI Revocation of PAI and VID-scoped PAA by Vendor #459
- DA PKI Revocation of non-VID scoped PAAs by Vendor #479
- Add a VID field for non-VID scoped PAAs (Root certificates) #477
- A transaction for assigning a VID to non-VID scoped PAAs (root certificates) #478
Upgrade procedure
- The release must be applied via cosmovisor and Upgrade Proposal transactions, see pool-upgrade-how-to.md.
- The upgrade name must be equal to
v1.2.0
. - The release must be applied to all nodes (Validators, Observers, Sentries, etc.)
- All upgraded nodes must be at 0.12.0 with cosmovisor enabled.
- It's recommended to enable the auto-download for cosmovisor on all nodes, see pool-upgrade-how-to.md.
- Adding new nodes to the running pool (Test Net in particular) must be done via one of the ways described in running-node-in-existing-network.md. Starting a new node from the genesis state will not work. There are instructions on how to add a new node to the
Pre-Release 1.2.0
Changes and Fixes (comparing to 0.12.0)
- Update DCL Code for Approval count to ceiling instead of round #409
- Feature: re-vote for pending #412
- Feature: remove a proposal by the owner #287
- Do not allow proposing Root certificate by non-Trustee #427
- Deletion of Model Versions #421
- Document subscribing to events via Tendermint WebSockets #414
- Adding a Model requires "partNumber" and "productLabel" but those attributes should be optional #429
- NFR: New Role with permission to add/update Vendor Info #430
- Edit of DCL Compliance entry #464
- Deletion of DCL Compliance entry #465
- Set OTA for existing Model #466
- DA PKI Revocation of PAI and VID-scoped PAA by Vendor #459
- DA PKI Revocation of non-VID scoped PAAs by Vendor #479
- Add a VID field for non-VID scoped PAAs (Root certificates) #477
- A transaction for assigning a VID to non-VID scoped PAAs (root certificates) #478
Upgrade procedure
- The release must be applied via cosmovisor and Upgrade Proposal transactions, see pool-upgrade-how-to.md.
- The upgrade name must be equal to
v1.2.0
. - The release must be applied to all nodes (Validators, Observers, Sentries, etc.)
- All upgraded nodes must be at 0.12.0 with cosmovisor enabled.
- It's recommended to enable the auto-download for cosmovisor on all nodes, see pool-upgrade-how-to.md.
- Adding new nodes to the running pool (Test Net in particular) must be done via one of the ways described in running-node-in-existing-network.md. Starting a new node from the genesis state will not work. There are instructions on how to add a new node to the