docs: close the roadmap page's release-history gap - #1052
Merged
Conversation
The site's roadmap narrates post-1.0 work in version bands — v0.1.4–v0.2.5, v0.2.6–v0.2.13, v0.2.14–v0.2.19 — and then stopped. The v0.2.51 refresh appended a paragraph with no band, which papered over thirty releases and left a reader thinking nothing shipped between the private-image work and now. Three things that did ship were missing entirely: step-up MFA, self-healing against external container changes, and the Activity section. Two bands added, checked against news.md rather than memory, plus a fix to the new paragraph's attribution: it credited scheduled ETL jobs to the latest work, but those shipped in v0.2.43, so they moved into the band where they belong. The final paragraph deliberately carries NO version band. Every candidate was wrong or self-ageing: a closing band would have to name the current release and go stale, and "latest"/"most recent" is exactly the trap that left `v0.2.x · latest` sitting in the roadmap diagram until this session. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up da #1051, encontrado ao verificar o site publicado em vez de confiar no build.
O que estava errado
A página de roadmap narra o pós-1.0 em faixas de versão —
v0.1.4 – v0.2.5,v0.2.6 – v0.2.13,v0.2.14 – v0.2.19— e parou ali. O refresh da v0.2.51 acrescentou um parágrafo sem faixa, o que encobria trinta releases: um leitor sai com a impressão de que nada aconteceu entre o trabalho de imagens privadas e agora.Três entregas reais estavam ausentes da narrativa: MFA step-up por app, o self-healing contra mudanças externas de container, e a seção Atividades. Conferi cada uma no
news.md, não na memória.O que mudou
Duas faixas novas cobrindo v0.2.20–v0.2.44 e v0.2.45–v0.2.49, mais uma correção de atribuição no parágrafo que a #1051 adicionou: ele creditava os cronjobs ao trabalho mais recente, mas eles saíram na v0.2.43 — foram para a faixa onde pertencem.
Uma decisão que vale explicar
O parágrafo final não leva faixa de versão, de propósito. Todas as opções eram ruins: fechar a faixa exigiria nomear a release atual e envelheceria na próxima; e
latestou "most recent" é precisamente a armadilha que deixouv0.2.x · latestparado no diagrama de roadmap até esta sessão, porque quem escreve não volta para atualizar. Sem faixa, o texto continua correto sozinho.mdbook build bookpassa.🤖 Generated with Claude Code