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

chore: upstream dfinity/icp-cli-recipes (static-site) moved to static-site-v0.4.0

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

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
74/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
documentation

Direzione di ricerca

Start with .agents/upstream-tracking.md and compare static-site-v0.3.3 with static-site-v0.4.0. Re-check the @dfinity/static-site examples in guides/frontends/, getting-started/, and references/application-canisters.md, then update any affected documentation and set pinned to static-site-v0.4.0 in .sources/upstream.json. Done means the reviewed pages are current and the pin is updated in the same PR, or the PR explains why only the pin changed.

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

Descrizione

upstream-dfinity-icp-cli-recipes-static-site upstream-sync

dfinity/icp-cli-recipes has moved past the ref the docs are verified against.
Pinned in .sources/upstream.json static-site-v0.3.3
Latest release static-site-v0.4.0
Compare https://github.com/dfinity/icp-cli-recipes/compare/static-site-v0.3.3...static-site-v0.4.0
Published reference https://github.com/dfinity/icp-cli-recipes/releases

What to re-check

The canister's own pages are synced from dfinity/certified-assets into docs/guides/frontends/static-site/ and follow that repo's releases, not this one, so a recipe release mainly moves the version readers pin: check the @dfinity/static-site@ examples in guides/frontends/, getting-started/ and references/application-canisters.md. This repo's own icp.yaml deploys with it, so a release also affects the docs site itself. Each recipe in this repo tags and releases on its own prefix, so it gets its own entry: a single pattern across prefixes would compare rust- against static-site- textually and only ever surface one of them.

How to close this

  1. Review the changes above against the pages named under "What to re-check".
  2. Update those pages if anything they state has changed.
  3. Set pinned to static-site-v0.4.0 in .sources/upstream.json in the same PR.

If nothing in the docs is affected, bump the pin on its own and say so in the PR.

Procedure: .agents/upstream-tracking.md

Lingua principale
JavaScript
Stelle
4
Fork
5
Merge medio
21h 45m
PR unite (30g)
28

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 dfinity/developer-docs

Tutte le issue di dfinity/developer-docs

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.