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

Publish every package through staged trusted publishing (owner approves each release)

Aperta
  • Qualcosa non va?
#42 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, nodejs
Ambito
ci-cd, release

Direzione di ricerca

Start with one publish-*.yml workflow (for example the agent-pay-openfort one, which already uses staged publishing) and compare it with a workflow still calling npm publish. Apply the npm stage publish change to the remaining package workflows and add a short section to docs/REVIEWING.md. Step 2, unticking "Allow npm publish" on npmjs.com, needs the owner, so a contributor should only prepare the workflow and docs changes. Done means every listed workflow stages its release, and the docs describe the approval flow.

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

Descrizione

@deepfirstsearch/agent-pay-openfort now publishes with npm trusted publishing and direct publishing off. The workflow runs npm stage publish (npm 12), and a version only goes live after the owner approves it on npmjs.com with 2FA. This was validated with 0.1.1 on 2026-10-09: the staged tarball was downloaded and diffed against a local build of the tag, and was identical.

The other packages (agent-pay, agent-pay-mcp, -ai-sdk, -langchain, -agentkit, -turnkey, -privy, -cdp, order-guard) still publish directly from their workflows. If a workflow or the repo were compromised, a release could go out unreviewed.

For each package:

  1. In its publish-*.yml, install npm 12 and replace npm publish with npm stage publish . --provenance --access public --ignore-scripts.
  2. On npmjs.com, untick "Allow npm publish" on its trusted publisher (owner only).
  3. Validate with the next release: download the staged tarball (npm stage download <id>), diff it against the tag build, then approve.

The publish flow also gets a short section in docs/REVIEWING.md.

Lingua principale
TypeScript
Stelle
0
Fork
0
Merge medio
3h 51m
PR unite (30g)
3

Preparare l'ambiente

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 DeepFirstHQ/deepfirstsearch

Tutte le issue di DeepFirstHQ/deepfirstsearch

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.