cosmossdk.io/client/v2@v2.0.0-beta.1/CHANGELOG.md (about)

     1  <!--
     2  Guiding Principles:
     3  
     4  Changelogs are for humans, not machines.
     5  There should be an entry for every single version.
     6  The same types of changes should be grouped.
     7  Versions and sections should be linkable.
     8  The latest version comes first.
     9  The release date of each version is displayed.
    10  Mention whether you follow Semantic Versioning.
    11  
    12  Usage:
    13  
    14  Change log entries are to be added to the Unreleased section under the
    15  appropriate stanza (see below). Each entry should ideally include a tag and
    16  the Github issue reference in the following format:
    17  
    18  * (<tag>) \#<issue-number> message
    19  
    20  The issue numbers will later be link-ified during the release process so you do
    21  not have to worry about including a link manually, but you can if you wish.
    22  
    23  Types of changes (Stanzas):
    24  
    25  "Features" for new features.
    26  "Improvements" for changes in existing functionality.
    27  "Deprecated" for soon-to-be removed features.
    28  "Bug Fixes" for any bug fixes.
    29  "Client Breaking" for breaking Protobuf, gRPC and REST routes used by end-users.
    30  "CLI Breaking" for breaking CLI commands.
    31  "API Breaking" for breaking exported APIs used by developers building on SDK.
    32  Ref: https://keepachangelog.com/en/1.0.0/
    33  -->
    34  
    35  # Changelog
    36  
    37  ## [Unreleased]
    38  
    39  ## [v2.0.0-beta.1] - 2023-11-07
    40  
    41  This is the first tagged version of client/v2.
    42  It depends on the Cosmos SDK v0.50 release and fully supports AutoCLI.