theupdateframework / theupdateframework/theupdateframework.io
Spec version list on the Specification page is missing v1.0.34, v1.0.35, and v1.0.36
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 25
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
The version list on the Specification page (content/en/spec.md) is hand-maintained, and it's fallen behind. It currently stops at v1.0.33, but the spec repo has since published three more releases:
- v1.0.34 — 2026-01-22
- v1.0.35 — 2026-07-15
- v1.0.36 — 2026-08-10 (less than a week old at time of writing)
Checked via the GitHub API against theupdateframework/specification releases — all three are real, published, non-draft, non-prerelease tags, so this isn't a case of them being intentionally left off.
For comparison, the canonical auto-generated list at /specification/list/ (redirects to theupdateframework.github.io/specification/) already has all three. So the drift is specific to this page's manual list, not the underlying source of truth — which means anyone landing on the main site's Specification page sees an outdated picture of what's current.
This is basically the exact failure mode #107 flagged back in 2024 ("is the idea that spec maintainers should update this page too when they make a specification release? This feels like unnecessary process") — it's now happened for real. Fixing #107 properly (generating the list instead of hand-maintaining it, or just linking out) would prevent this from recurring. In the meantime the list at minimum needs the three missing entries added.
One more thing I noticed while checking: v1.0.21 is also absent from this page's list, but it's missing from the canonical /specification/list/ page too, so that one looks intentional (probably a retracted release) rather than a bug on this site — not raising that part, just noting it so no one goes looking.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open content/en/spec.md and locate the hand-maintained Specification version list. Compare it with the releases or canonical list at /specification/list/, then update the page so v1.0.34, v1.0.35, and v1.0.36 appear with their published dates. Done means the main Specification page shows all three missing releases and does not add the separately absent v1.0.21.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 84/100