Merge pull request #194 from casper-ecosystem/version-bump-1.2

Version bump 1.2

CHANGELOG.md

@@ -13,13 +13,23 @@ All notable changes to this project will be documented in this file.  The format
 
 ### Added
 
-* Added a new modality named `EventsMode` that dictates how the installed instance of CEP-78 will handle the recording of events. Refer to the README for further details
+* Added a new modality named `EventsMode` that dictates how the installed instance of CEP-78 will handle the recording of events. Refer to the [README](./README.md#eventsmode) for further details
 
-* Added the ability to define additional `NFTMetadataKind`s as either `additional_required_metadata` or `optional_metadata`. Refer to the `Installing the Contract` section of the README for more information on using these arguments.
+* Added the ability for the contract to specify one or more metadata schemas, with the option to further specify optional metadata schemas. Additional required metadatas are specified by `additional_required_metadata`, while additional optional metadata schemas can be specified using `optional_metadata`. Refer to the [`Installing the Contract`](./README.md#installing-the-contract) section of the README for more information on using these arguments.
 
 * When upgrading from a contract instance, you may now change the `total_token_supply` to a number higher than the current number of minted tokens, but lower than your previous total. The number cannot be zero. More information is available in the upgrade tutorials.
 
-* Added the ability to revoke approval.
+* Added a new entrypoint called `revoke` that allows token owners to revoke a single approval.
+
+* Added a new entrypoint `is_approval_for_all` that allows a caller to check if they are considered an `operator` for a token owner.
+
+* For js-client changes, please view the respective [change log](./client-js/CHANGELOG.md).
+
+### Changed
+
+* `OwnerReverseLookupMode` now contains an additional option, `TransfersOnly`, which begins tracking ownership upon transfer. More information can be found [here](./README.md#ownerreverselookupmode).
+
+* Optimized the `set_approval_for_all` entrypoint implementation to reduce gas costs.
 
 ## Release 1.1.1
 

README.md

@@ -260,7 +260,7 @@ This modality provides the following options:
 
 1. `NoLookup`: The reporting and receipt functionality is not supported. In this option, the contract instance does not maintain a reverse lookup database of ownership and therefore has more predictable gas costs and greater scaling.
 2. `Complete`: The reporting and receipt functionality is supported. Token ownership will be tracked by the contract instance using the system described [here](#owner-reverse-lookup-functionality).
-3. `TransfersOnly`: The reporting and receipt functionality is supported alike `Complete` however it is not directly active after minting but only after a first transfer. This modality is for usecases where the majority of NFTs are owned by a private minter and only NFT's that have been transferred benefit from reverse lookup tracking. Token ownership will be as well tracked by the contract instance using the system described [here](#owner-reverse-lookup-functionality).
+3. `TransfersOnly`: The reporting and receipt functionality is supported like `Complete`. However, it does not begin tracking until the first transfer. This modality is for usecases where the majority of NFTs are owned by a private minter and only NFT's that have been transferred benefit from reverse lookup tracking. Token ownership will also be tracked by the contract instance using the system described [here](#owner-reverse-lookup-functionality).
 
 Additionally, when set to `Complete`, causes a receipt to be returned by the `mint` or `transfer` entrypoints, which the caller can store in their account or contract context for later reference.
 

client-js/CHANGELOG.md

@@ -9,7 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
-- Added support for CEP47Events
+- Added support for CEP47 Events
 - Added support for CES events basing on ces-js-parser
 - Some small code cleanups (added typings etc)
 - Some changes in `examples/`
@@ -30,5 +30,4 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Fixed
 
-- Fixed how `migrate` deploy is constructed.
-
+- Fixed how `migrate` deploy is constructed.

client/balance_of_session/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "balance_of_session"
-version = "1.1.1"
+version = "1.2.0"
 edition = "2018"
 
 [dependencies]

client/get_approved_session/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "get_approved_session"
-version = "1.1.1"
+version = "1.2.0"
 edition = "2018"
 
 [dependencies]

client/is_approved_for_all_session/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "is_approved_for_all_session"
-version = "1.1.1"
+version = "1.2.0"
 edition = "2018"
 
 [dependencies]

client/mint_session/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "mint_session"
-version = "1.1.1"
+version = "1.2.0"
 edition = "2018"
 
 [dependencies]

client/owner_of_session/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "owner_of_session"
-version = "1.1.1"
+version = "1.2.0"
 edition = "2018"
 
 [dependencies]

client/transfer_session/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "transfer_session"
-version = "1.1.1"
+version = "1.2.0"
 edition = "2021"
 
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

client/updated_receipts/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "updated_receipts"
-version = "1.1.1"
+version = "1.2.0"
 edition = "2021"
 
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

contract/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "contract"
-version = "1.1.1"
+version = "1.2.0"
 edition = "2018"
 
 [dependencies]

tests/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "tests"
-version = "1.1.1"
+version = "1.2.0"
 edition = "2018"
 
 [dependencies]