chore: Release V0.1.11

[MonaaEid]

No description provided.

[github-actions]

Hi @MonaaEid, this is **LinkBot** 👋

Linking pull requests to issues helps us significantly with reviewing pull requests and keeping the repository healthy.

🚨 This pull request does not have an issue linked.

Please link an issue using the following format:

• Fixes chore: [StepSecurity] Apply security best practices hiero-ledger/hiero-sdk-python#123

📖 Guide:
docs/sdk_developers/how_to_link_issues.md

If no issue exists yet, please create one:
docs/sdk_developers/creating_issues.md

Thanks!

[coderabbitai]

Walkthrough

Added a new CHANGELOG entry for version "0.1.11 - 2026-02-11" noting two test files reformatted with Black, and removed sparse-checkout configuration from the release PR workflow .github/workflows/release-pr-coderabbit-gate.yml.

Changes

Cohort / File(s)	Summary
Changelog Update CHANGELOG.md	Added version 0.1.11 - 2026-02-11 entry documenting Black formatting of tests/unit/crypto_utils_test.py and tests/unit/entity_id_helper_test.py.
CI Workflow .github/workflows/release-pr-coderabbit-gate.yml	Removed sparse-checkout and related cone-mode settings from the checkout step so the repository is no longer sparsely checked out.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided, but the changeset is self-evident from the title and files modified (CHANGELOG and release workflow).	Add a brief description explaining the release purpose, contents, or any breaking changes included in v0.1.11.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly indicates a release version bump (0.1.11), which matches the changelog entry and workflow changes that prepare for the release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch coderabbit-release-TESTttt

---

No actionable comments were generated in the recent review. 🎉

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Read the release PR prompt instructions
cat .github/coderabbit/release-pr-prompt.md

Length of output: 56

---

🏁 Script executed:

#!/bin/bash
# Check if the file exists and read it
if [ -f ".github/coderabbit/release-pr-prompt.md" ]; then
    cat .github/coderabbit/release-pr-prompt.md
else
    echo "File not found. Searching for it..."
    fd release-pr-prompt.md
fi

Length of output: 56

---

🏁 Script executed:

#!/bin/bash
# Read the file using the path found by fd
cat hiero-sdk-python/.github/coderabbit/release-pr-prompt.md

Length of output: 88

---

🏁 Script executed:

#!/bin/bash
# Check the repository structure
pwd
ls -la
echo "---"
# Find all markdown files in .github
fd -e md . .github 2>/dev/null || find .github -name "*.md" 2>/dev/null || echo "No .github directory found"

Length of output: 1537

---

🏁 Script executed:

#!/bin/bash
# Read the release prompt file
cat .github/coderabbit/release-pr-prompt.md

Length of output: 56

---

🏁 Script executed:

#!/bin/bash
# Check file details and try different reading methods
ls -lh .github/coderabbit/release-pr-prompt.md
echo "---"
# Try with head
head -n 100 .github/coderabbit/release-pr-prompt.md
echo "---"
# Check file type
file .github/coderabbit/release-pr-prompt.md

Length of output: 194

---

🏁 Script executed:

#!/bin/bash
# Verify the file content with xxd or od
echo "File content:"
cat .github/coderabbit/release-pr-prompt.md | od -c
echo "---"
# Read CHANGELOG.md to see the release notes
echo "CHANGELOG.md excerpt:"
head -n 50 CHANGELOG.md
echo "---"
# Read RELEASE.md
echo "RELEASE.md:"
cat RELEASE.md

Length of output: 4608

---

🏁 Script executed:

#!/bin/bash
# Check version in pyproject.toml
echo "=== pyproject.toml version ==="
grep -A 2 "^\[project\]" pyproject.toml | head -10

echo -e "\n=== Git diff summary ==="
git diff --stat origin/main...HEAD

echo -e "\n=== Files changed ==="
git diff --name-only origin/main...HEAD

echo -e "\n=== CHANGELOG.md changes ==="
git diff origin/main...HEAD -- CHANGELOG.md | head -100

Length of output: 887

---

🏁 Script executed:

#!/bin/bash
# Check how version is managed
echo "=== Looking for version definition ==="
grep -r "version" pyproject.toml | head -20
echo ""
grep -r "__version__" src/ 2>/dev/null | head -10

echo -e "\n=== Workflow file changes ==="
git diff origin/main...HEAD -- .github/workflows/release-pr-coderabbit-gate.yml

echo -e "\n=== Recent git tags ==="
git tag --sort=-version:refname | head -10

echo -e "\n=== Full CHANGELOG diff ==="
git diff origin/main...HEAD -- CHANGELOG.md

Length of output: 1418

---

@github-actions[bot], I've completed the release-gate review for version 0.1.11.

✅ Release Review Summary

Version: 0.1.11 (PATCH)
Date: 2026-02-11
Release Type: Test Formatting Updates

Changes in this Release

This PR adds only a version header to CHANGELOG.md. The actual changes under this version (test formatting with Black) were already present in the changelog under the Unreleased section.

Review Findings

✅ CHANGELOG Format: Properly formatted following Keep a Changelog standard
✅ Semantic Versioning: PATCH version increment is appropriate (only test formatting changes)
✅ No Breaking Changes: No functional code changes detected
✅ Documentation: All test formatting changes are documented with PR references

Technical Notes

1. Version Management: This project uses setuptools-scm for dynamic versioning based on git tags. The version will be properly set when the release tag is created after merging.

2. Workflow Optimization: The PR also removes sparse-checkout configuration from the release-gate workflow, which should improve checkout performance.

3. No Git Tags: The repository currently has no tags. After merging, create the tag v0.1.11 as documented in RELEASE.md to complete the release process.

⚠️ Note About Base Reference

The bot correctly notes that the base ref (main) doesn't look like a release tag. Since this appears to be the first automated release process run and no previous tags exist, this is expected. Future releases should compare against the previous version tag (e.g., v0.1.10...v0.1.11).

Recommendation

✅ Approve and merge - This release follows the documented release process and contains only non-functional test formatting improvements.

After merging, remember to:

1. Create and push the git tag: git tag -a v0.1.11 -m "Release 0.1.11"
2. Push the tag: git push origin v0.1.11