Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
#413 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
74/100
Type d'issue
Documentation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
javascript
Domaine
documentation

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
JavaScript
Étoiles
4
Forks
5
Merge moyen
21 h 45 min
PR mergées (30 j)
28

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de dfinity/developer-docs

Toutes les issues de dfinity/developer-docs

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.