Skip to content

ci: pin docs-engine to v0.3.0 for the default Contributing page - #5

Merged
burinc merged 1 commit into
mainfrom
ci/bump-docs-engine-v0.3.0
Sep 7, 2026
Merged

burinc merged 1 commit into
mainfrom
ci/bump-docs-engine-v0.3.0

Conversation

@burinc

@burinc burinc commented Sep 7, 2026

Copy link
Copy Markdown
Collaborator

docs-engine v0.3.0 (jlt-commons/docs-engine#2) adds an automatic Contributing page to every project's generated guide. It's purely additive, needs no config change, and a project's own docs/guide/contributing.md still overrides it.

This project's site.yml calls the shared jlt-commons/ci-builds/.github/workflows/site.yml@main workflow, whose docs-engine-ref input still defaults to v0.2.0. Pinning it explicitly to v0.3.0 here is what actually gets the new page onto this project's live site, and keeps the build reproducible even if the shared default moves again later.

Same change already landed as prior art in jlt-commons/raylib-android#8.

docs-engine v0.3.0 adds an automatic Contributing page to every
project's generated guide, purely additive and overridable by a
project's own docs/guide/contributing.md. The shared site workflow
still defaults docs-engine-ref to v0.2.0, so picking up the new page
on this project's live site needs an explicit pin rather than waiting
on the shared default to move.

Pinning explicitly also means this project's site build stays
reproducible even after that default moves again later.

Same change already landed in jlt-commons/raylib-android#8.
@burinc
burinc merged commit 0fc3f16 into main Sep 7, 2026
4 checks passed
@burinc
burinc deleted the ci/bump-docs-engine-v0.3.0 branch September 7, 2026 04:54
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