Skip to content

Pre-Release 1.2.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@ashcherbakov ashcherbakov released this 07 Aug 16:45
· 340 commits to master since this release
v1.2.0
c1081db
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Changes and Fixes (comparing to 0.12.0)

  1. Update DCL Code for Approval count to ceiling instead of round #409
  2. Feature: re-vote for pending #412
  3. Feature: remove a proposal by the owner #287
  4. Do not allow proposing Root certificate by non-Trustee #427
  5. Deletion of Model Versions #421
  6. Document subscribing to events via Tendermint WebSockets #414
  7. Adding a Model requires "partNumber" and "productLabel" but those attributes should be optional #429
  8. NFR: New Role with permission to add/update Vendor Info #430
  9. Edit of DCL Compliance entry #464
  10. Deletion of DCL Compliance entry #465
  11. Set OTA for existing Model #466
  12. DA PKI Revocation of PAI and VID-scoped PAA by Vendor #459
  13. DA PKI Revocation of non-VID scoped PAAs by Vendor #479
  14. Add a VID field for non-VID scoped PAAs (Root certificates) #477
  15. 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
Assets 8
Loading