chore: sync lichess-api submodule to 572cea5 (external engine docs fix) - #31
Merged
Conversation
Sync vendored OpenAPI spec to upstream commit 572cea5 ("fix external
engine docs inaccuracy").
The single upstream commit is documentation-only:
- Adds blank lines after the endpoint header line in three external
engine tag descriptions (markdown formatting).
- Corrects the prose in POST /api/external-engine/work to reference
the `providerSecret` request field instead of `secret`.
No endpoints, DTO fields, enums, or error responses changed. The
request-body schema already used `providerSecret`, and the litchee
client already sends that field, so no client code changes are
required.
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.
Summary
Automated upstream sync of the vendored Lichess OpenAPI spec submodule (
reference/lichess-api).3033570("Update API version")572cea5("fix external engine docs inaccuracy")There is exactly one upstream commit in this range, and it is documentation-only.
Spec changes detected
The upstream commit touches three External Engine tag files under
doc/specs/tags/externalengine/:api-external-engine-id-analyse.yamlapi-external-engine-work-id.yamlapi-external-engine-work.yamlsecret" to "registered with the givenproviderSecret".No endpoints, request/response DTO fields, enums, error responses, or the API version were changed. In particular, the request-body schema of
POST /api/external-engine/workalready declared the field asproviderSecret; only the surrounding description text had the wrong name.Client impact
None required. The litchee external engine client (
src/api/engine/external_engine.rs) already sends the correct field:So the client already matches the corrected spec. This PR is limited to the submodule pointer bump so the vendored spec stays in lockstep with upstream.
Verification
Run in the project toolchain:
cargo fmt --check— cleancargo clippy --all-targets --all-features -- -D warnings— cleancargo test— all unit, integration, and doc tests passGenerated by Claude Code