Skip to content

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

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
Contributor

What

Pins this project's site build to docs-engine v0.3.0 via the shared
docs-engine-ref input on jlt-commons/ci-builds/.github/workflows/site.yml@main,
which currently defaults to v0.2.0.

Why

v0.3.0 adds an automatic Contributing page to every generated site.
It's purely additive, needs no config, and any project can override
it with its own docs/guide/contributing.md. Pinning the ref
explicitly is what actually gets that page onto this project's live
site, rather than waiting for the shared workflow's own default to
move.

Pinning also keeps the build reproducible: a future bump of the
shared default won't silently change what this repo publishes until
the pin here is bumped on purpose.

Verification

docs/check-site.sh asserts specific named pages by path and doesn't
count total pages, so the new Contributing page shouldn't trip it.
The new page only lands in the guide's root directory, so this
project's nested docs/guide/adr/ is untouched. CI on this PR is the
authoritative check.

Prior art

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

Pinning it also keeps this project's site build reproducible: a
future bump of the shared default won't silently change what this
repo publishes until the pin is bumped on purpose.

Mirrors jlt-commons/raylib-android#8.
@burinc
burinc merged commit cd3b36d 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