Before next release: bring main's 0.2.0 changes into develop and fix the setup guide's broken install link

Open
  • Is something wrong?
#282 2 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@umeradl is already working on this.

Since Oct 26, 2026.

  • #294 by @Abidoyesimze — open

Assessment

This issue has not been assessed yet.

Description

bug documentation

Problem

  • The dincli 0.2.0 release (2409664, 19 Aug) and its setup-guide fix (f423611) were made directly on main and haven't been brought into develop yet. main has 32 commits not on develop.
  • As a result, develop is still at version = "0.1.0", and Documentation/public/setup.md on develop (Option A) links .../refs/heads/main/dist/dincli-0.1.0-py3-none-any.whl, which no longer exists on main (main has dist/dincli-0.2.0-*). The README and the org landing page link to develop's docs, so new participants hit this on step one.
  • Option B (pip install git+...@main#subdirectory=dist) can't work on either branch, because dist/ isn't a Python project directory.
  • If develop is merged into main as it stands, the merge would conflict and could roll main's version back from 0.2.0 to 0.1.0.

Most of main's other direct fixes (CID verification, chain-id validation, bridge-eth, Python 3.12 floor, LICENSE) were already re-applied on develop. Still on main only: the 0.2.0 bump/dist and the CPU/CUDA requirements split.

Suggested fix (keeps our develop → main workflow)

  1. Bring main's direct changes into develop (merge main into develop), keeping both main's release fixes and develop's newer work where they overlap.
  2. Bump develop to 0.3.0, so the next develop → main merge moves main forward.
  3. Fix setup.md on develop: point Option A at a GitHub Release asset (or a tagged install, e.g. pip install git+https://github.com/InfiniteZeroFoundation/[email protected]), fix Option B, and test on a clean machine.
  4. Then merge develop into main as usual. Going forward, make fixes on develop first so main doesn't drift ahead.
Dominant language
Python
Stars
4
Forks
7
Avg merge
4d 9h
Merged PRs (30d)
35

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 InfiniteZeroFoundation/DevNet

All issues in InfiniteZeroFoundation/DevNet

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.