Skip to content

v1.4.0

Compare
Choose a tag to compare
@Abdulbois Abdulbois released this 09 Jul 08:49
· 30 commits to master since this release
202c388

Changes and Fixes (comparing to 1.2.2)

  • #303 Upgrade Cosmos SDK, tendermint, golang and project dependencies
  • #523 PID scoped Accounts
  • Add NOC root certificate transactions design doc
  • Update the NOC root certificate design based on discussion feedback
  • #519 Query Certificates with subjectKeyId
  • Update the NOC root certificate design
  • #535 Enable providing serial number while revoking x509 certs
  • #535 Add transaction command to remove non-root certificates
  • #524 Implement adding and requesting root NOC certificates
  • Support for forward and backward compatibility in DCL schemes
  • #535 Make the revocation of child certificates optional
  • #535 Enable checking VID matchings while adding x509 certificate
  • #535 Enable adding non-root NOC(ICA) certificates
  • #535 Enhancements to Adding, Revoking, and Removing Non-Root Certificates
  • #524 Enable revocation of NOC root certificates
  • #524 Enable revocation of NOC non-root certificates
  • #502 Add SchemaVersion field into PKI, Compliance, Model and VendorInfo schemas
  • #538 Add commissioner remote UI flow url field into model schema
  • Update transactions.md document
  • #531 Publish pai certificates for crl signer certificate verification
  • Refactor update tests for sequential version upgrades starting from initial version
  • Set CommissioningModeInitialStepsHint to 1 by default for standard flow
  • Query NOC Root certificates by VID and SKID by
  • #560 Enable removing NOC ICA certificates
  • #524 Enable removing NOC root certificates
  • Add instructions on how to use the Ledger Nano with DCL
  • Improve error message texts
  • Add schemaVersion field into NOC/ICA and auxiliary models
  • #575 Rename CommissionerRemoteUiFlowUrl to ManagedAclExtensionRequestFlowUrl
  • #547 Add new fields into Model entity
  • Correct transactions documentation

Full Changelog: v1.2.2...v1.4.0

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.4.
  • The release must be applied to all nodes (Validators, Observers, Sentries, etc.)
  • All upgraded nodes must be at 1.2.2 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.