Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
#1,625 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
20/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
docker, git, github-actions
Domínio
ci-cd, devops, release

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Dart
Estrelas
23
Forks
1
Merge médio
31min
PRs com merge (30d)
570

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de QueryaHub/Querya-Desktop

Todas as issues de QueryaHub/Querya-Desktop

Issues semelhantes

Mais issues de Dart

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.