From 20b52cc0470b05a8ac18357e4dec4e731e3460d7 Mon Sep 17 00:00:00 2001
From: Damian Nolan <damiannolan@gmail.com>
Date: Tue, 12 Sep 2023 16:42:40 +0200
Subject: [PATCH] chore: adding changelog to mod/capability (#4627)

* chore: adding changelog to mod/capability

* Update modules/capability/CHANGELOG.md

Co-authored-by: Cian Hatton <cian@interchain.io>

---------

Co-authored-by: Cian Hatton <cian@interchain.io>
---
 modules/capability/CHANGELOG.md | 58 +++++++++++++++++++++++++++++++++
 1 file changed, 58 insertions(+)
 create mode 100644 modules/capability/CHANGELOG.md

diff --git a/modules/capability/CHANGELOG.md b/modules/capability/CHANGELOG.md
new file mode 100644
index 00000000000..cf6d1b30cae
--- /dev/null
+++ b/modules/capability/CHANGELOG.md
@@ -0,0 +1,58 @@
+<!--
+Guiding Principles:
+Changelogs are for humans, not machines.
+There should be an entry for every single version.
+The same types of changes should be grouped.
+Versions and sections should be linkable.
+The latest version comes first.
+The release date of each version is displayed.
+Mention whether you follow Semantic Versioning.
+Usage:
+Change log entries are to be added to the Unreleased section under the
+appropriate stanza (see below). Each entry should ideally include a tag and
+the Github issue reference in the following format:
+* (<tag>) \#<issue-number> message
+The issue numbers will later be link-ified during the release process so you do
+not have to worry about including a link manually, but you can if you wish.
+Types of changes (Stanzas):
+"Features" for new features.
+"Improvements" for changes in existing functionality.
+"Deprecated" for soon-to-be removed features.
+"Bug Fixes" for any bug fixes.
+"Client Breaking" for breaking CLI commands and REST routes used by end-users.
+"API Breaking" for breaking exported APIs used by developers building with this module.
+"State Machine Breaking" for any changes that result in a different AppState given the same genesisState and txList.
+Ref: https://keepachangelog.com/en/1.0.0/
+-->
+
+# Changelog
+
+## [Unreleased]
+
+### Dependencies
+
+* [\#4068](https://github.com/cosmos/ibc-go/pull/4068) Upgrade capability module to cosmos-sdk v0.50
+
+### API Breaking
+
+### State Machine Breaking
+
+### Improvements
+
+* [\#4068](https://github.com/cosmos/ibc-go/pull/4068) Various improvements made to testing to reduce the dependency tree and use new cosmos-sdk test utils.
+
+### Features
+
+### Bug Fixes
+
+* [\#15030](https://github.com/cosmos/cosmos-sdk/pull/15030) `InitMemStore` now correctly uses a `NewInfiniteGasMeter` for both `GasMeter` **and** `BlockGasMeter`. This fixes an issue where the `gasMeter` was incremented non-deterministically across validators. See [\#15015](https://github.com/cosmos/cosmos-sdk/issues/15015) for more information.
+
+## Capability in the Cosmos SDK Repository
+
+The capability module was originally released in [v0.40.0](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.40.0) of the Cosmos SDK.
+Please see the [Release Notes](https://github.com/cosmos/cosmos-sdk/blob/v0.40.0/RELEASE_NOTES.md).
+
+The capability module has been removed from the Cosmos SDK from `v0.50.0` onwards and has been migrated to this repository. 
+It will now be maintained as a standalone go module. 
+
+Please refer to the Cosmos SDK repository for historical content.
\ No newline at end of file