[Good First Issue]: Update Solo Version to v0.58.0

[rwalworth]

🆕🐥 First-Time Friendly

This issue is especially welcoming for people who are new to contributing to the Hiero Swift SDK.

We know that opening your first pull request can feel like a big step.
Issues labeled Good First Issue are designed to make that experience easier, clearer, and more comfortable.

No prior knowledge of Hiero, Hedera, or distributed ledger technology is required.
Just a basic familiarity with Swift and Git is more than enough to get started.

👾 Description of the Issue

The CI workflow file:

.github/workflows/swift-ci.yml

uses hiero-solo-action to spin up a local Hiero Solo network for running integration tests.

The soloVersion parameter is currently set to v0.56.0, but a newer version (v0.58.0) is now available.

Keeping the Solo version up to date ensures that integration tests run against the latest local network tooling, catching any compatibility issues early and staying aligned with upstream improvements.

💡 Proposed Solution

Update the soloVersion value in .github/workflows/swift-ci.yml from v0.56.0 to v0.58.0.

The changes should:

• Only modify the soloVersion value
• Not change any other workflow configuration, steps, or parameters
• Not affect SDK behavior or public APIs

👩‍💻 Implementation Steps (End-to-End)

To complete this change:

• Open .github/workflows/swift-ci.yml
• Locate the Prepare Hiero Solo step (around line 111)
• Find the soloVersion parameter, which currently reads:

  soloVersion: v0.56.0

• Update it to:

  soloVersion: v0.58.0

• Save the file and verify no other lines were changed
• Commit and push your changes

CI will run automatically when you open a pull request and will validate that the updated Solo version works correctly with the existing integration tests.

✅ Acceptance Criteria

To merge a pull request for this issue:

• Scope: Changes are limited to updating the soloVersion value in .github/workflows/swift-ci.yml
• Behavior: No SDK behavior or public API changes
• Tests: Existing CI checks pass (unit tests and integration tests)
• Review: All code review feedback addressed

📋 Step-by-Step Contribution Guide

To help your first contribution go as smoothly as possible, we recommend following these steps:

• Comment /assign to request the issue
• Wait for assignment
• Fork the repository and create a branch
• Set up the project by following the instructions in README.md
• Make the requested changes
• Sign each commit using -s -S
• Push your branch and open a pull request

Read Workflow Guide for step-by-step workflow guidance.
Read README.md for setup instructions.

Important: Pull requests cannot be merged without S and s signed commits.
See the Signing Guide.

🤔 Additional Information

If you need help, reach out to the @hiero-ledger/hiero-sdk-good-first-issue-support team.

You can also join our community on Discord:
Hiero Discord

Maintainers are happy to help first-time contributors succeed!

[ambicuity]

Created PR #579 to resolve this issue by updating the soloVersion to v0.58.0 as requested.

[rwalworth]

Hi @ambicuity, thanks for your enthusiasm! You are assigned. As a note for the future, please wait until you're assigned to an issue before you begin working on it, thanks!