ci: pin docs-engine to v0.3.0 for the default Contributing page - #8
Merged
Conversation
jlt-commons/ci-builds' shared site.yml still defaults to v0.2.0. Pinning here explicitly, rather than waiting for that default to move, is what actually gets the new guide/contributing.html onto this project's published site. Verified locally against the merged v0.3.0 checkout before pinning: raylib-android's own docs/check-site.sh passes against the build (4 guide pages now, up from 2; 33 images unchanged).
This was referenced Sep 7, 2026
burinc
added a commit
to jlt-commons/glitter-uikit
that referenced
this pull request
Sep 7, 2026
docs-engine v0.3.0 adds an automatic Contributing page to every project's generated guide, with no config needed and no override in place here. The shared site.yml workflow still defaults to v0.2.0, so pinning this project's docs-engine-ref explicitly is what actually gets the new page onto glitter-uikit's live site, and it also keeps this build reproducible if that shared default moves again later. Same change already landed in jlt-commons/raylib-android#8.
burinc
added a commit
to jlt-commons/glitter-gl
that referenced
this pull request
Sep 7, 2026
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 site.yml workflow still defaults its docs-engine-ref input to v0.2.0, so this project needs an explicit pin to actually pick up the new page on its published site. Pinning here rather than relying on the shared default also keeps this project's build reproducible the next time that default moves. Same pattern already landed in jlt-commons/raylib-android#8.
burinc
added a commit
to jlt-commons/glitter
that referenced
this pull request
Sep 7, 2026
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.yml reusable workflow still defaults docs-engine-ref to v0.2.0, so pinning it here explicitly is what actually gets the new page onto this project's live site. Pinning also keeps the build reproducible: once the shared default moves past v0.3.0, this project won't pick up a later version until someone bumps the pin on purpose. Same change as jlt-commons/raylib-android#8.
burinc
added a commit
to jlt-commons/awesome-jolt
that referenced
this pull request
Sep 7, 2026
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.yml workflow's docs-engine-ref input still defaults to v0.2.0, so this project won't pick up the new page until it pins the newer version itself. Pinning explicitly, rather than tracking the shared workflow's default, also keeps this project's build reproducible the next time that default moves. Same pattern already landed in jlt-commons/raylib-android#8.
burinc
added a commit
to jlt-commons/ebb
that referenced
this pull request
Sep 7, 2026
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
added a commit
to jlt-commons/raygui-jlt
that referenced
this pull request
Sep 7, 2026
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.
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.
docs-engine v0.3.0 (jlt-commons/docs-engine#2) adds a default
guide/contributing.htmlto every project's site. The sharedci-builds/site.ymlstill defaults to v0.2.0, so this pins explicitly rather than waiting for that default to move.Verified locally: built against the merged v0.3.0 checkout,
docs/check-site.shpasses (4 guide pages now, up from 2).