Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
hlnd2t/trigger-release-buildSegurança de jogos e anti-cheat

trigger-release-build

⁨Safely dispatch an immutable source-owned Release verification or publication from the current origin/main SHA. Use only when explicitly asked to verify, publish, or rebuild a game version.⁩

v2026.11.13-dcf20203 instalações+3 em 7 dias67 EstrelasMITsincronizado há 11 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install hlnd2t/trigger-release-build

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
deNAY/k04s…5CmH0oDg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote6be040b0…0c866980
6be040b0141f…e3bc0c8669803 arquivos · ⁦5.1 KB⁩
VarreduraMédio3 achados
  • injection.no_confirmationSKILL.md:48
  • Script executável junto com a skillscripts/trigger_release_build.py
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/HLND2T/CS2_VibeSignatures/tree/main/.claude/skills/trigger-release-build@dcf2020

Este item ainda não foi escrito no seu idioma, então aparece em English.

Use the bundled script as the only remote-operation entry point. Do not construct an ad-hoc gh workflow run command, accept a user-supplied SHA, move a tag, edit a Release, cancel work, or bypass CI source-artifact preflight.

The local script checks repository/auth access, version selection, duplicate work, and the current origin/main SHA. It does not create a temporary worktree or run full source-artifact preflight locally. All build paths retain their CI source-artifact gates before building or publishing; artifact validation failures are reported in the Actions run.

Procedure

  1. Confirm both release choices with the user before any remote work. Ask two separate questions and do not dispatch until both are answered explicitly — never choose on the user's behalf, never preselect an option, and never infer an answer from a previous run.

    • Build path: offer all three choices:
      • release: fresh -force_all rebuild, with automatic prior-version artifact/signature reuse when available.
      • full-rebuild: fresh -force_all -oldgamever none rebuild of every configured artifact into an empty external output root. No oldgamever artifacts are used as references or old-signatures sources. The execution report must prove no prior GAMEVER and an isolated old-artifact root. Source-controlled preprocessor references remain available; tracked artifacts for the target GAMEVER remain the verification and publication truth.
      • rebuild-free: manual emergency path that binds tracked bin_artifacts/<GAMEVER> without proving rebuildability.
    • Publication: verify-only (verify candidates without publishing), publish (publish without replacing existing content), or republish (replace an existing mutable Release in place, retaining its ID and tag name). In Claude Code, ask with the AskUserQuestion tool, offering the available choices on each question.
  2. Extract the requested game version, or use latest only when the user explicitly asks for the latest version.

  3. Map the confirmed answers onto the script flags: --mode <verify-only-or-publish-or-republish>, plus --workflow full-rebuild or --workflow rebuild-free when the user chose that path. Omit --workflow for release. full-rebuild dispatches the standard build workflow with source_artifact_mode=full-rebuild.

  4. Run from any directory with the confirmed mode stated explicitly:

    powershell
    uv run python .claude/skills/trigger-release-build/scripts/trigger_release_build.py <GAMEVER-or-latest> --mode <verify-only-or-publish-or-republish> [--workflow <release-or-full-rebuild-or-rebuild-free>]
  5. Report the script's selected version, publication mode, workflow, full SOURCE_SHA, commit subject, and Actions run URL.

  6. If the script refuses the operation, surface its exact safety reason and stop. Do not bypass repository, auth, version, duplicate-work, or origin/main checks. Do not bypass a failed CI source-artifact gate.

publish preserves existing content and supports exact-byte retries. Select republish only when the user explicitly requests replacement: it moves the tag to the selected source, updates metadata and assets, and temporarily makes the Release a draft. Upload/verification failures leave a draft for a rerun to resume; do not silently switch modes or retry with a different source. A fresh dispatch uses the then-current origin/main, so use the existing Actions run's rerun when the same bundle is required. A missing target requires publish; GitHub immutable Releases cannot be republished. Any requested generator/config change must already be merged into origin/main with its complete bin_artifacts/<GAMEVER> tree.

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosSimSim
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaPrompt injection · injection.no_confirmationSKILL.md:48
  2. MédiaArquivo · Script executável junto com a skillscripts/trigger_release_build.py
  3. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-dcf202013 de nov. de 2026dcf20206be040b0Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login