version bump (#486)

Author: ozgunozerk

Cargo.lock

@@ -37,7 +37,7 @@ repository = "https://github.com/OpenZeppelin/stellar-contracts"
 documentation = "https://docs.openzeppelin.com/stellar-contracts/"
 keywords = ["stellar", "soroban", "smart-contracts", "standards"]
 categories = ["no-std", "wasm"]
-version = "0.5.0"
+version = "0.5.1"
 
 [workspace.dependencies]
 soroban-sdk = "23.0.2"

Cargo.toml

@@ -54,9 +54,9 @@ We recommend pinning to a specific version, because rapid iterations are expecte
 
 ```toml
 [dependencies]
-stellar-tokens = "=0.5.0"
-stellar-access = "=0.5.0"
-stellar-contract-utils = "=0.5.0"
+stellar-tokens = "=0.5.1"
+stellar-access = "=0.5.1"
+stellar-contract-utils = "=0.5.1"
 ```
 
 ## Notes

README.md

@@ -137,9 +137,9 @@ Add this to your `Cargo.toml`:
 ```toml
 [dependencies]
 # We recommend pinning to a specific version, because rapid iterations are expected as the library is in an active development phase.
-stellar-access = "=0.5.0"
+stellar-access = "=0.5.1"
 # Add this if you want to use macros
-stellar-macros = "=0.5.0"
+stellar-macros = "=0.5.1"
 ```
 
 ## Examples

packages/access/README.md

@@ -132,7 +132,7 @@ Policies follow a well-defined lifecycle that integrates with context rule manag
 
 **Enforcement** is triggered when a context rule successfully matches. Once all policies in the matched rule pass their `can_enforce()` checks, the smart account calls `enforce()` on each policy. This state-changing hook allows policies to update counters, emit events, record timestamps, or perform other mutations that track authorization activity. For example, a spending limit policy might deduct from the available balance and emit an event documenting the transaction.
 
-**Uninstallation** occurs when a context rule is removed from the smart account. The account calls `uninstall()` on each attached policy, allowing them to clean up any stored data associated with that specific account and context rule pairing. This ensures that policies do not leave orphaned state in storage. 
+**Uninstallation** occurs when a context rule is removed from the smart account. The account calls `uninstall()` on each attached policy, allowing them to clean up any stored data associated with that specific account and context rule pairing. This ensures that policies do not leave orphaned state in storage.
 
 #### Policy Examples
 
@@ -288,7 +288,7 @@ Add this to your `Cargo.toml`:
 ```toml
 [dependencies]
 # We recommend pinning to a specific version, because rapid iterations are expected as the library is in an active development phase.
-stellar-accounts = "=0.5.0"
+stellar-accounts = "=0.5.1"
 ```
 
 ### 2. Implement the Smart Account Trait

packages/accounts/README.md

@@ -133,9 +133,9 @@ Add this to your `Cargo.toml`:
 ```toml
 [dependencies]
 # We recommend pinning to a specific version, because rapid iterations are expected as the library is in an active development phase.
-stellar-contract-utils = "=0.5.0"
+stellar-contract-utils = "=0.5.1"
 # Add this if you want to use macros
-stellar-macros = "=0.5.0"
+stellar-macros = "=0.5.1"
 ```
 
 ## Examples

packages/contract-utils/README.md

@@ -22,7 +22,7 @@ pub struct MyContract;
 #[contractimpl]
 impl FungibleToken for MyContract {
     type ContractType = Base;
-    
+
     // Only provide overrides here, default implementations are auto-generated
 }
 ```
@@ -167,7 +167,7 @@ Add this to your `Cargo.toml`:
 ```toml
 [dependencies]
 # We recommend pinning to a specific version, because rapid iterations are expected as the library is in an active development phase.
-stellar-macros = "=0.5.0"
+stellar-macros = "=0.5.1"
 ```
 
 ## Examples

packages/macros/README.md

@@ -135,9 +135,9 @@ Add this to your `Cargo.toml`:
 ```toml
 [dependencies]
 # We recommend pinning to a specific version, because rapid iterations are expected as the library is in an active development phase.
-stellar-tokens = "=0.5.0"
+stellar-tokens = "=0.5.1"
 # Add this if you want to use macros
-stellar-macros = "=0.5.0"
+stellar-macros = "=0.5.1"
 ```
 
 ## Examples