Skip to content

ci: update Solo version used in CI tests#2733

Open
imshubham22apr-gif wants to merge 4 commits into
hiero-ledger:mainfrom
imshubham22apr-gif:ci/update-solo-version
Open

ci: update Solo version used in CI tests#2733
imshubham22apr-gif wants to merge 4 commits into
hiero-ledger:mainfrom
imshubham22apr-gif:ci/update-solo-version

Conversation

@imshubham22apr-gif

Copy link
Copy Markdown
Contributor

What does this PR do?

Updates the Solo version used in CI workflows from v0.65.0 to v0.68.0.

Why is this needed?

The current version in the workflows is outdated. This change aligns the CI setup with the version referenced in recent updates and discussions (see #2699).

What is included?

  1. Updated all occurrences of soloVersion in .github/workflows/build.yml
  2. Ensured consistency across the workflow file
  3. No other changes made to CI logic

Notes :-

  1. The selected version (v0.68.0) matches the version used in related updates and avoids introducing unverified changes
  2. Happy to update further if a different version is preferred....

@imshubham22apr-gif imshubham22apr-gif requested a review from a team as a code owner May 2, 2026 06:53
@codacy-production

codacy-production Bot commented May 2, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

Signed-off-by: Aashish Pandit <imshubham.22apr@gmail.com>
@imshubham22apr-gif imshubham22apr-gif force-pushed the ci/update-solo-version branch from a7c74b3 to e4b9560 Compare May 2, 2026 07:30
@mustafauzunn

Copy link
Copy Markdown
Contributor

Some tests are failing

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes skip the example if we don't get the estimates. Also we don't need the try/catch blocks.
The correct approach here would be a retry mechanism or a wait time

@imshubham22apr-gif

Copy link
Copy Markdown
Contributor Author

@mustafauzunn The changes have been made according to your review. I have removed the try/catch blocks and implemented a retry mechanism for FeeEstimateQuery. Could you please review it again?

Signed-off-by: imshubham22apr-gif <imshubham.22apr@gmail.com>
@mustafauzunn

Copy link
Copy Markdown
Contributor

Run ./gradlew spotlessApply to fix format issue

TransferTransaction tx = createTransferTransaction(client, recipientId);
FeeEstimateResponse stateEstimate = estimateWithStateMode(client, tx);
FeeEstimateResponse intrinsicEstimate = estimateWithIntrinsicMode(client, tx);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Delete the new lines here and on line 66

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants