Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Fechada
  • Algo errado?
#413 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
74/100
Tipo de issue
Documentação
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
javascript
Domínio
documentation

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
JavaScript
Estrelas
4
Forks
5
Merge médio
1d 16h
PRs com merge (30d)
21

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de dfinity/developer-docs

Todas as issues de dfinity/developer-docs

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.