Skip to content

chore(deps): pin Sphinx build dependencies to exact versions#62

Merged
sbaerlocher merged 2 commits into
mainfrom
chore/pin-antsibull-docs
Jun 15, 2026
Merged

chore(deps): pin Sphinx build dependencies to exact versions#62
sbaerlocher merged 2 commits into
mainfrom
chore/pin-antsibull-docs

Conversation

@sbaerlocher

Copy link
Copy Markdown
Member

Summary

  • requirements.txt used loose lower-bound specifiers (antsibull-docs >=2.24.0,<3.0.0, sphinxcontrib-mermaid>=2.0.2, sphinx-sitemap>=2.9.0), so two checkouts could resolve to different versions.
  • Pin all build dependencies to exact versions for reproducible builds. The pinned versions equal the current latest releases, so this is a no-functional-change hardening.
  • Renovate keeps them current via the pip manager from the org renovate-base preset (already extended in .github/renovate.json).

Test plan

  • CI Build Documentation (incl. linkcheck) green with the pinned versions
  • Secret scan green

Notes

From the Notion "Repo Ideas" backlog for guide. This closes the last actionable guide idea; the remaining backlog cards (facet search, incremental builds) were closed as low-ROI.

requirements.txt used loose lower-bound specifiers for antsibull-docs,
sphinxcontrib-mermaid, and sphinx-sitemap, so two checkouts could
resolve different versions. Pin all build dependencies to exact
versions for reproducible builds. Renovate keeps them current via the
pip manager from the org renovate-base preset.

Signed-off-by: Simon Bärlocher <s.baerlocher@sbaerlocher.ch>
Comment thread requirements.txt Outdated
claude[bot]
claude Bot previously approved these changes Jun 15, 2026

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean, low-risk hardening. The three direct build dependencies that previously used range/lower-bound specifiers (antsibull-docs, sphinxcontrib-mermaid, sphinx-sitemap) are now exact-pinned, consistent with the already-pinned ansible-pygments and sphinx-ansible-theme. Verified there's no duplication with versions.env (collection versions only) and that Renovate is configured via the org renovate-base preset to bump these pins.

One non-blocking nit left inline: pinning only direct deps leaves the transitive tree unpinned, so "reproducible builds" is partial — a constraints/lock file would close that gap if full reproducibility is the goal. Not a blocker.

Address review feedback: the comment claimed 'reproducible builds',
but only the direct dependencies are pinned — transitive deps still
float. Reword to scope the claim to direct deps and note a pip-compile
constraints file as the follow-up if the floating tree causes drift.

Signed-off-by: Simon Bärlocher <s.baerlocher@sbaerlocher.ch>

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All raised issues have been addressed. The comment in requirements.txt now correctly scopes the pins to direct dependencies and explicitly documents that transitive deps are intentionally left floating, with a clear path forward if that ever causes problems.

@sbaerlocher sbaerlocher merged commit 55fabbe into main Jun 15, 2026
6 checks passed
@sbaerlocher sbaerlocher deleted the chore/pin-antsibull-docs branch June 15, 2026 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant