dusk-network / dusk-network/node-installer
Only inform about updates that affect current node network variant
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 38
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Some nodes are receiving information about a new version of the node installer being available, even though this version is intended for e.g., the testnet. Updating does nothing.
Possible Solution (optional)
Update the version check logic to be network-aware (devnet, testnet, mainnet), so that version notifications are only shown when a newer release is available for the node network variant.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the installer’s version check logic and how it identifies the current network variant. Verify the behavior for devnet, testnet, and mainnet: notifications should appear only when a newer release exists for the active variant, and updating should remain meaningful.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100