Publishing is a manual tag push, and the drift is what produced yesterday's 404s
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
No se nombra ningún archivo, prueba ni punto de entrada del workflow. Empieza por inspeccionar cómo los tags publish* activan actualmente la publicación en este repositorio y en las ediciones .fa, .fr y .zh-cn; después, compara las opciones de merge, programación y detección de divergencias. Se considera terminado cuando exista una política acordada y un comportamiento coordinado que limite la obsolescencia en todas las ediciones.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
The pattern
Every repository in this series publishes only when someone pushes a publish* tag — this repo and the .fa, .fr and .zh-cn editions alike. Merging to main changes nothing a reader can see.
That is a deliberate design and it has real merits: publishing is expensive, and a manual gate means someone decides when the site changes. But the gate is currently the only thing scheduling publication, and in practice it drifts. State as of this morning, before today's round of tags:
| Repository | Last published | Days stale |
|---|---|---|
| lecture-python-programming | 2026-07-16 | 18 |
.fa |
2026-06-19 | 45 |
.fr |
2026-07-17 | 17 |
.zh-cn |
2026-06-19 | 45 |
This repo had three lecture-affecting commits on main that no reader could see.
What that drift actually cost
Three things surfaced yesterday that all trace back to it, and none of which looked like a publishing problem at first:
polars 404'd in every language for four days. Added here on 2026-07-30 in #408, synced to all three translated editions and merged into each within the hour. Content and _toc.yml entries were correct everywhere. It was still 404 on all four sites — including this one — purely because nothing had been tagged since. The first read of that evidence was "the translations have not caught up", which was wrong; the English site did not have it either.
A wrong canonical stayed live for 45 days. The .zh-cn edition was emitting the English URL as its canonical on every page, telling search engines the entire Chinese edition was a duplicate of this one. Fixed in .zh-cn#80, but the fix only reached readers when that edition was finally tagged.
Divergence windows are set by tag timing, not translation speed. Sync PRs across all three editions merge in 8 minutes to 2 days, nearly always within the hour. Publishing lags by weeks. So when the language switcher advertises a page some edition does not have, the gap is almost entirely publish cadence — an inversion of the assumption I first wrote up in QuantEcon/action-translation#239, which had to be rewritten after measuring.
Yesterday's round is the counter-example: all four editions were tagged within about two minutes, all four builds succeeded in roughly six, and the switcher, the canonical fixes and polars all landed everywhere simultaneously. No divergence window opened at all. That is what good looks like, and it happened because someone did four things by hand in one sitting.
Worth considering
Not a concrete proposal — the right answer depends on how much manual control you want to keep:
- Publish on merge to
main, with the tag retained for deliberate re-publishes. Maximum freshness, least control. - Scheduled publish — a weekly or nightly cron that tags if
mainhas moved. Bounds staleness without publishing on every merge. - Keep it manual but make drift visible — a check that opens or comments on an issue when
mainis more than N days or M commits ahead of the last publish tag. Cheapest, and it addresses the actual failure, which is that nobody knew. - Whatever is chosen, coordinate the editions. The translated sites should publish close to this one. Their content is usually ready within the hour; it is the tags that spread them weeks apart.
The last point is the one I would weight most. The individual staleness is survivable; the editions drifting apart is what produces reader-visible breakage now that they cross-link.
Related
- QuantEcon/action-translation#239 — asks for a check that detects switcher and
hreflangtargets returning 404. Largely a symptom of this; worth less if publishing becomes regular. - QuantEcon/quantecon-book-theme#421 — language-aware 404 page, which softens the reader-facing half of the same window.
- Lenguaje dominante
- JavaScript
- Estrellas
- 75
- Forks
- 36
- Merge medio
- 37 min
- PR fusionados (30 d)
- 3
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de QuantEcon/lecture-python-programming
-
pandas: mean imputation corrupts Argentina's GDP per capita in the later plotQuizá libre de nuevo @omiiikb07 la tomó hace 11 días y no hay ningún pull request abierto. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
QuantEcon/lecture-python-programming#658 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 95/100
Todos los issues de QuantEcon/lecture-python-programming
Issues similares
-
bug frontend good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
oscarbol09/thesisforge#61 ·
-
bug status: needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
mastra-ai/mastra#31093 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
osmlab/name-suggestion-index#13165 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
ReduxISU/Redux_Frontend#327 ·
Los mantenedores suelen responder en 4 días
-
Remove hardcoded personal Auth0 tenant and live AUDIENCE from committed .env.development templateAbiertoenhancement ready-for-agent
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100