Merge branch 'main' into 939-AccountCreateTransaction-support-PrivateKey

Signed-off-by: AntonioCeppellini <128388022+AntonioCeppellini@users.noreply.github.com>

Author: AntonioCeppellini

.github/workflows/examples.yml

@@ -19,7 +19,7 @@ jobs:
           egress-policy: audit
 
       - name: Checkout repository
-        uses: actions/checkout@1af3b93b6815bc44a9784bd300feb67ff0d1eeb3
+        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8
         with:
           fetch-depth: 0
 

.github/workflows/pr-check-changelog.yml

@@ -12,7 +12,7 @@ jobs:
   changelog-check:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@1af3b93b6815bc44a9784bd300feb67ff0d1eeb3 # v6.0.0
+      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
         with:
           fetch-depth: 0
 

.github/workflows/publish.yml

@@ -23,7 +23,7 @@ jobs:
           egress-policy: audit
 
       - name: Checkout repository
-        uses: actions/checkout@1af3b93b6815bc44a9784bd300feb67ff0d1eeb3 # v6.0.0
+        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
 
       - name: Set up Python
         uses: actions/setup-python@83679a892e2d95755f2dac6acb0bfd1e9ac5d548 # v6.1.0

.github/workflows/test.yml

@@ -27,7 +27,7 @@ jobs:
           egress-policy: audit
 
       - name: Checkout repository
-        uses: actions/checkout@1af3b93b6815bc44a9784bd300feb67ff0d1eeb3 # v6.0.0
+        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
 
       - name: Set up Python ${{ matrix.python-version }}
         uses: actions/setup-python@83679a892e2d95755f2dac6acb0bfd1e9ac5d548 # v6.1.0

CHANGELOG.md

@@ -7,23 +7,44 @@ This changelog is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.
 ## [Unreleased]
 
 ### Added
+-
 
+### Changed
+-
+
+### Fixed
+-
+
+### Breaking Change
+-
+
+## [0.1.10] - 2025-12-03
+
+### Added
+- Added docs/sdk_developers/training/workflow: a training for developers to learn the workflow to contribute to the python SDK.
+- Added Improved NFT allowance deletion flow with receipt-based status checks and strict `SPENDER_DOES_NOT_HAVE_ALLOWANCE` verification.
 - Add `max_automatic_token_associations`, `staked_account_id`, `staked_node_id` and `decline_staking_reward` fields to `AccountUpdateTransaction` (#801)
 - Added docs/sdk_developers/training/setup: a training to set up as a developer to the python sdk
 - Add example demonstrating usage of `CustomFeeLimit` in `examples/transaction/custom_fee_limit.py`
 - Added `.github/workflows/merge-conflict-bot.yml` to automatically detect and notify users of merge conflicts in Pull Requests.
-- Added `.github/workflows/bot-office-hours.yml` to automate the Weekly Office Hour Reminder.  
+- Added `.github/workflows/bot-office-hours.yml` to automate the Weekly Office Hour Reminder.
 - feat: Implement account creation with EVM-style alias transaction example.
 - Added validation logic in `.github/workflows/pr-checks.yml` to detect when no new chnagelog entries are added under [Unreleased]
 - feat: AccountCreateTransaction now supports both PrivateKey and PublicKey [#939]
+- Added validation logic in `.github/workflows/pr-checks.yml` to detect when no new chnagelog entries are added under [Unreleased].
+- Support for message chunking in `TopicSubmitMessageTransaction`.
 
 ### Changed
+
 - bot workflows to include new changelog entry
 - Removed duplicate import of transaction_pb2 in transaction.py
+- Refactor `TokenInfo` into an immutable dataclass, remove all setters, and rewrite `_from_proto` as a pure factory for consistent parsing [#800]
 - feat: Add string representation method for `CustomFractionalFee` class and update `custom_fractional_fee.py` example.
 - Moved query examples to their respective domain folders to improve structure matching.
 
+
 ### Fixed
+
 - fixed workflow: changelog check with improved sensitivity to deletions, additions, new releases
 
 ## [0.1.9] - 2025-11-26
@@ -66,6 +87,7 @@ This changelog is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.
 - Add `set_token_ids`, `_from_proto`, `_validate_checksum` to TokenAssociateTransaction [#795]
 - docs: added `network_and_client.md` with a table of contents, and added external example scripts (`client.py`).
 
+
 ### Changed
 
 - Upgraded step-security/harden-runner v2.13.2

docs/sdk_developers/training/workflow/01_supporting_infrastructure.md

@@ -0,0 +1,61 @@
+## Supporting Infrastructure When Developing for the Python SDK
+
+For the best development experience and smoother support, we strongly recommend installing the following tools when developing for the Python SDK:
+
+Recommended Tools
+- [ ] GitHub Desktop
+- [ ] Visual Studio Code
+    - [ ] Pylance
+    - [ ] GitHub Copilot
+
+However, what may work best for you might be different. 
+
+### Github Desktop
+GitHub Desktop is a free, user-friendly application that provides a visual interface for Git and GitHub. Instead of running Git commands in a terminal, GitHub Desktop lets you perform common tasks through an intuitive UI.
+
+It allows you to:
+- Clone, fork, and manage repositories without using the command line
+- Easily create and switch branches
+- Visualize commit history and branches in a clear, interactive timeline
+- Stage and push local changes with a click
+- Resolve merge conflicts with guided prompts
+
+Overall, GitHub Desktop makes Git simpler, safer, and more visual, which is great for maintaining clean, branched pull requests and staying aligned with the rest of the Python SDK team.
+
+### VS Studio Code
+VS Code is a workpace that enables:
+
+- Easy project navigation
+- Easy file organisation
+- Access to a large ecosystem of extensions that plug-in, including Pylance and Github Copilot
+
+It’s the recommended editor for working within this SDK.
+
+#### Pylance
+Pylance is a high-performance language server for Python that:
+
+- Improves code quality
+- Identifies errors early
+- Helps you resolve issues faster
+
+For example, Pylance will underline this in red indicating it is incorrect with a reason:
+```python
+from hiero_sdk_python.account.token_id import TokenId
+```
+This is incorrect because token_id.py does not live in /account! Instead, it lives in /tokens
+
+Read our [Pylance Installation Guide](../../pylance.md)
+
+#### Github Copilot
+Github Copilot is an AI coding-assistant tool.
+
+GitHub Copilot supports your workflow by:
+- Suggesting code snippets and patterns
+- Helping predict correct imports
+- Maintaining consistent naming and formatting
+- Speeding up development
+
+Additionally, since we have Copilot enabled as an automatic reviewer, once you enable Copilot as a reviewer, it will review your pull requests submitted to the Python SDK. This helps maintainers merge changes more quickly and is a great benefit to the project.
+
+
+

docs/sdk_developers/training/workflow/02_forking_python_sdk.md

@@ -0,0 +1,35 @@
+## Forking the Python SDK
+
+To begin contributing to the Python SDK, you’ll first need your own copy of the repository.
+
+Forking creates a personal, editable version of the SDK under your own GitHub account, where you can safely experiment and prepare pull requests without impacting the Python SDK.
+
+### Steps to Fork the Python SDK
+
+1. Navigate to the Python SDK Repository
+
+Open the [Official Python SDK repository on GitHub](https://github.com/hiero-ledger/hiero-sdk-python)
+
+2. Create Your Fork
+Make sure you are logged in to Github. Then, in the top-right of the repository page, click Fork.
+
+GitHub will prompt you to confirm:
+- The destination account (your profile)
+- The name you want to give your fork (you can keep the default)
+
+Click Create fork.
+
+Your new fork will appear at:
+`https://github.com/<your-username>/<repository-name>`
+This is your copy of the Python SDK. You can also access it from your repository section on github online.
+
+
+3. Clone Your Fork Locally
+
+You now have an online copy of the Python SDK but you also need a local copy to work on the code.
+
+Using GitHub Desktop (recommended):
+1. Open GitHub Desktop.
+2. Go to File → Clone Repository
+3. Select the fork you just created under the “Your Repositories” tab.
+4. Choose a folder location on your machine and click Clone.

docs/sdk_developers/training/workflow/03_staying_in_sync.md

@@ -0,0 +1,32 @@
+## Syncing Your Repo with the Upstream Python SDK
+
+Development at the Python SDK can be fast meaning new changes are added frequently.
+
+It is important to frequently pull new changes at the Python SDK to your local repository to ensure you are working on the most updated code and avoid merge_conflicts.
+
+To do this:
+
+1. Link the Upstream Python SDK Remote with yours
+Link your fork to the upstream original Python SDK repository so you can easily bring in new updates from main.
+
+```bash
+git remote add upstream https://github.com/hiero-ledger/hiero-sdk-python.git
+```
+
+Then verify it is correctly set:
+```bash
+git remote -v
+```
+
+You should now see:
+origin → your fork
+upstream → the official Python SDK repo
+
+2. Before starting work and during a pull request, always fetch new changes:
+git checkout main
+git fetch upstream
+git pull upstream main
+
+Then rebase on your working branch to apply the new changes:
+git checkout mybranch
+git rebase main -S

docs/sdk_developers/training/workflow/04_assigning_issues.md

@@ -0,0 +1,12 @@
+## Getting Assigned to an Issue
+
+It is important to be assigned an issue before starting work on it or creating a pull request.
+
+We recommend Good First Issues for developers new to the Python SDK. These are easier and better documented tasks.
+
+To do that, 
+1. Select a `Good First Issue` that interests you and is not yet assigned at [Python SDK Issues](https://github.com/hiero-ledger/hiero-sdk-python/issues)
+2. Write a comment at the bottom of the issue page asking "I want to be assigned to this issue"
+3. A maintainer will shortly assign you to the issue
+
+Congratulations! You are assigned and can now get started on the work.

docs/sdk_developers/training/workflow/05_working_branches.md

@@ -0,0 +1,21 @@
+## Working on a Newly Assigned Issue in a Branch
+
+Once you are assigned to an issue, you can get started working on it.
+
+We require developers to work on a new branch for each new issue they are working on. This helps to avoid major sync issues and keep history clean.
+
+Before you create a branch, remember to pull in all recent changes from main:
+```bash
+git checkout main
+git fetch upstream
+git pull upstream main
+```
+
+Then create a branch:
+```bash
+git checkout -b my-new-branch-name
+```
+
+Commit all your changes on this new branch, then publish your branch and submit a pull request.
+
+