Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Port published API data loading to the v13 website branch

Abierto
#1,433 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions

Línea de trabajo

Start from PR #1432 to see how the published-data loader consumes the v12 publication, then find the equivalent loader and the data/api/v13.* files on the website's v13 branch. Check the branch's deployment workflow to confirm that API-data pushes trigger a build. Done means a v13 build from a compiler-generated snapshot renders the root and module routes, documentation, and sidebar, and rejects an invalid publication.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

The compiler publishes versioned API snapshots to the website repository's default branch. PR #1432 makes website master consume the latest v12 publication, but the website's v13 branch also needs a loader that consumes published v13 data before compiler v13 CI and releases can target that branch.

Target branch: website v13.

  • Port or adapt the published-data loader from #1432 to the v13 branch's layout.
  • Configure the documentation major as v13 and keep the displayed version, route generation, sidebar, page content, and API link validation consistent.
  • Require a complete selected snapshot with valid library roots and module fields; fail invalid publications during the build.
  • Consume the repository-root data/api/v13.* publications, with no reads from obsolete snapshot copies.
  • Verify that API-data pushes to v13 trigger its website deployment; adapt the branch's deployment workflow if needed.

Acceptance: build the v13 website using a compiler-generated v13 snapshot; verify its root and module routes, documentation, and sidebar entries. Cover major/version selection and invalid publications, and run the applicable website CI checks.

Land this before switching compiler v13 publication to website branch v13.

Related: #1391, #1421, and #1432.

Coordinated compiler follow-up: rescript-lang/rescript #8753. That workflow change depends on this website preparation.

Lenguaje dominante
MDX
Estrellas
1.9k
Forks
260
Merge medio
1 d 2 h
PR fusionados (30 d)
35

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de rescript-lang/rescript-lang.org

Todos los issues de rescript-lang/rescript-lang.org

Issues similares

Más issues de DevOps

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.