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

extension authors: adopt --strict, publish the action, verify the Release hooks (after #1487)

Abierto
#1,625 2 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, git, github-actions
Área
ci-cd, devops, release

Línea de trabajo

Start with docs/extension-registry.md and the linked work in #1487 and #1621. This issue spans release hooks, extension-template and registry workflows, action publishing, and a Codespaces or other-host check of Docker-in-Docker; several steps depend on a release and external organization settings. Done means completing the applicable checklist, verifying the release and template runs, and updating hosts.json when the version should become permanent.

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

Descripción

enhancement

Left over from #1487. Everything here waits for the first release that contains the new tester and the Release hooks (they reach main with the next dev → main merge).

After that release
  • Release hooks: the run after the Release workflow logged told QueryaHub/extensions and told QueryaHub/extension-template (secret QUERYA_DISPATCH_TOKEN is set). A manual Run workflow with an already published version does the same check. In the registry a Publish run by repository_dispatch appears and compat.json gets a column for the version.
  • Template follow-up: QueryaHub/extension-template pushed querya-<version> and opened a pull request (or an issue, if the organization still forbids Actions to open pull requests). Merge it, and check that the Test run on the branch is green.
  • --strict is in the tester (#1621). In QueryaHub/extension-template replace the "Fail if the plugin ran without the sandbox" JUnit grep with strict: "true" of the action, and the same in QueryaHub/extensions (.github/actions/test-record).
  • Publish QueryaHub/action-test-extension@v1 (a copy of .github/actions/test-extension, now with strict), then point the template and the registry at it instead of QueryaHub/Querya-Desktop/.github/actions/test-extension@<sha>.
  • Raise hosts.json in QueryaHub/extensions when the new version should become a permanent column of compat.json.
Not done and not blocked by a release
  • devcontainer up on the template, with Docker-in-Docker and the compose file, ending in a green querya-ext-tester ./dist --connect ... --sandbox, was only checked in parts (the Feature installs and the tester passes in the container; the nested Docker daemon did not start on a host without the iptables nat table). Check it in Codespaces or on another host.
  • Optional: let GitHub Actions open pull requests in the organization (Settings → Actions → General), so the template's release pull request is not an issue.
  • Optional: replace the personal access token behind QUERYA_DISPATCH_TOKEN with a GitHub App token, so the hooks do not stop when the person or the token expires.

See docs/extension-registry.md.

Lenguaje dominante
Dart
Estrellas
23
Forks
1
Merge medio
31 min
PR fusionados (30 d)
570

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 QueryaHub/Querya-Desktop

Todos los issues de QueryaHub/Querya-Desktop

Issues similares

Más issues de Dart

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.