Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#104 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
docker, github-actions, go
Área
ci-cd, cli, documentation, release

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Go
Estrellas
1
Forks
1
Merge medio
5 d 2 h
PR fusionados (30 d)
3

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TMHSDigital/subenum

Todos los issues de TMHSDigital/subenum

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.