Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#413 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
74/100
Issue-Typ
Dokumentation
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
javascript
Bereich
documentation

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
JavaScript
Sterne
4
Forks
5
Ø Merge
21 Std. 45 Min.
Gemergte PRs (30 T.)
28

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus dfinity/developer-docs

Alle Issues in dfinity/developer-docs

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.