Skip to content

[Good First Issue]: Upgrade solo version to v0.72.0 in CI workflow #1570

Description

@rwalworth

🆕🐥 First-Time Friendly

This issue is especially welcoming for people who are new to contributing to the Hiero C++ 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 C++ and Git is more than enough to get started.

Important

📋 About Good First Issues

Good First Issues are designed to make getting started as smooth and stress-free as possible.

They usually focus on:

  • Small, clearly scoped changes
  • Straightforward updates to existing code or docs
  • Simple refactors or clarity improvements

Other kinds of contributions — like larger features, deeper technical changes, or design-focused work — are just as valuable and often use the beginner, intermediate, or advanced labels.

👾 Description of the Task

The CI workflow currently pins Hiero Solo to v0.71.0. Version v0.72.0 is now available and should be used to keep the integration test environment current.

The version is set in a single line of the reusable build workflow:

.github/workflows/zxc-build-library.yaml

Relevant line (line 201):

soloVersion: v0.71.0

This is a direct string replacement — no C++ knowledge or SDK architecture understanding is needed.

💡 Proposed Approach

Update the soloVersion value in .github/workflows/zxc-build-library.yaml from v0.71.0 to v0.72.0. No other files need to change.

👩‍💻 Implementation Steps

  • Open .github/workflows/zxc-build-library.yaml
  • Locate line 201 (search for soloVersion)
  • Replace v0.71.0 with v0.72.0
  • Confirm no other occurrences of v0.71.0 remain in the file
  • Open a pull request with the change

✔️ Acceptance Criteria

  • soloVersion in .github/workflows/zxc-build-library.yaml is set to v0.72.0
  • No other files are modified
  • No unrelated changes are introduced

📋 Step-by-Step Contribution Guide

To help keep contributions consistent and easy to review, 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 using 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.

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

🤔 Additional Information

If you have questions while working on this issue, feel free to ask!

You can reach the community and maintainers here: Hiero-SDK-C++ Discord

Whether you need help finding the right file, understanding existing code, or confirming your approach — we're happy to help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: lowNon-urgent tasks, nice-to-have improvements, or minor issuesscope: ciRelated to GitHub Actions, automated testing workflows, or CI/CD pipelinesskill: good first issueSimple, well-scoped tasks ideal for someone new to the repository or open sourcestatus: ready for devFully defined and ready for a contributor to pick up

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions