Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Problem: binary version of node instances is ambiguous

Open
#546 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

The issue names the CLI entry point ./kwild --version; start by tracing how that command builds its version string and review related issue #544. Done means the output provides an unambiguous version signal that can determine whether running nodes are up to date.

Written by the indexing model from the issue text.

Description

When checking whether the binary is updated or not we use --version in CLI to get its version. However, the current preview branch always returns kwild version 0.8.3+release. when we want to check whether something is already being updated or not. We might need a way to check if the running nodes are indeed the most updated ones.

./kwild --version
kwild version 0.8.3+release.

related: https://github.com/truflation/tsn/issues/544

cc @brennanjl @outerlook

Dominant language
Go
Stars
7
Forks
3
Avg merge
3h 2m
Merged PRs (30d)
13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from trufnetwork/node

All issues in trufnetwork/node

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.