Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Cut v0.9.0: the site, README and docs describe 49 unreleased commits, so the landing-page commands fail on @latest

Chiusa
  • Qualcosa non va?
#104 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
docker, github-actions, go
Ambito
ci-cd, cli, documentation, release

Direzione di ricerca

Read the GoReleaser pipeline referenced by #61, the Pages deployment workflow, and the documented commands in README.md, docs/index.html, docs/start.md, docs/labs.md, docs/monitoring.md, docs/library.md, and docs/cli.md. First check the latest tag and compare its published assets and behavior with main. Done when the release, container, pkg.go.dev package, and documented commands match the stated checks and future Pages updates cannot advertise unreleased behavior.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: docs area: release bug documentation priority: high

Why it matters

Every new visitor's first command fails. v0.8.0 is the latest tag, main is 49 commits ahead, and the Pages site (rebuilt in bd2aa16 and redeployed on every push to main) documents the unreleased behaviour. That undercuts the "honest tool" positioning the site is built on.

Evidence (checked against a v0.8.0 build)

  • subenum -simulate example.com (landing CTA, docs/index.html:224) exits 1 on v0.8.0 because -w is still required; the bundled 5k wordlist (data/subdomains-5k.txt) is unreleased.
  • -stats is an unknown flag in v0.8.0, so the hero command and the jq -e '.verdict == "complete"' gate fail.
  • DoT/DoH, -simulate-zone (docs/labs.md), -diff (docs/monitoring.md), takeover hints, resume, permute, config/env defaults: all only on main.
  • https://pkg.go.dev/github.com/TMHSDigital/subenum/pkg/subenum is 404 because no tag contains pkg/; docs/library.md:12 go get gives a module without the package.
  • "Static builds for ... FreeBSD" (docs/index.html:26, docs/start.md:21) and gh attestation verify subenum_<version>_linux_amd64.tar.gz (README.md:201) match no published v0.8.0 asset (v0.8.0 assets are the old subenum-linux-amd64 naming).

Suggested approach

  1. Tag v0.9.0 from main via the GoReleaser pipeline (#61). This also closes #46 and should include #102 (CITATION.cff version).
  2. Prevent recurrence: deploy Pages on release: published (or from the latest tag) rather than every push, or add a CI job that runs the docs' copy-paste commands against the @latest release.
  3. Optionally mark newer flags with "since vX.Y" in docs/cli.md.

Done when

  • go install github.com/TMHSDigital/subenum@latest && subenum -simulate example.com -stats s.json works.
  • ghcr.io/tmhsdigital/subenum:latest has the same flags.
  • pkg.go.dev resolves pkg/subenum.
  • The release lists FreeBSD archives, checksums.txt, SBOM and attestations matching README instructions.
Lingua principale
Go
Stelle
1
Fork
1
Merge medio
5g 2h
PR unite (30g)
3

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di TMHSDigital/subenum

Tutte le issue di TMHSDigital/subenum

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.