Auto-SDK Version Pumped To 0.4.0

[clostao]

PR Type

enhancement

---

Description

• Bumped the version of the Auto-SDK packages from 0.3.0 to 0.4.0.
• Updated the @autonomys/auto-utils dependency to version ^0.4.0 across multiple packages.
• Updated gitHead to reflect the new commit hash in all package.json files.

---

Changes walkthrough 📝

Relevant files

Enhancement

lerna.json Bump Lerna version to 0.4.0                                                            lerna.json Updated version from 0.3.0 to 0.4.0. +1/-1      package.json Update auto-consensus package to version 0.4.0                      packages/auto-consensus/package.json Updated package version from 0.3.0 to 0.4.0. Updated dependency @autonomys/auto-utils version to ^0.4.0. Updated gitHead to new commit hash. +3/-3      package.json Update auto-id package to version 0.4.0                                    packages/auto-id/package.json Updated package version from 0.3.0 to 0.4.0. Updated dependency @autonomys/auto-utils version to ^0.4.0. Updated gitHead to new commit hash. +3/-3      package.json Update auto-utils package to version 0.4.0                              packages/auto-utils/package.json Updated package version from 0.3.0 to 0.4.0. Updated gitHead to new commit hash. +2/-2      package.json Update auto-xdm package to version 0.4.0                                  packages/auto-xdm/package.json Updated package version from 0.3.0 to 0.4.0. Updated dependency @autonomys/auto-utils version to ^0.4.0. Updated gitHead to new commit hash. +3/-3

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Update the "gitHead" to the correct commit hash Ensure that the "gitHead" value is updated to the correct commit hash that reflects the state of the repository after the changes made in this pull request. packages/auto-utils/package.json [40] -"gitHead": "60e178a2c02aff3693007a1620e2067856a389f8" +"gitHead": "<correct_commit_hash>" Suggestion importance[1-10]: 8 Why: Ensuring the "gitHead" reflects the correct commit hash is important for maintainability and traceability of changes, especially in a version-controlled environment.	8
Best practice	Use fixed versions for dependencies to ensure consistent builds Consider using a fixed version instead of a version range for the dependency "@autonomys/auto-utils" to ensure consistent builds and avoid potential breaking changes that could be introduced by minor version updates. packages/auto-consensus/package.json [24] -"@autonomys/auto-utils": "^0.4.0" +"@autonomys/auto-utils": "0.4.0" Suggestion importance[1-10]: 7 Why: Using a fixed version instead of a version range can help ensure consistent builds and avoid potential breaking changes from minor updates. However, it may limit flexibility in receiving non-breaking updates automatically.	7