chore: sync vendored Lichess API spec to 2.0.154 (submodule 90055ff) - #32
Open
obazin wants to merge 1 commit into
Open
chore: sync vendored Lichess API spec to 2.0.154 (submodule 90055ff)#32obazin wants to merge 1 commit into
obazin wants to merge 1 commit into
Conversation
Updates the vendored Lichess OpenAPI spec submodule from 572cea5 to 90055ff. The only spec change under doc/specs/ is the API version bump 2.0.153 -> 2.0.154; schemas/ and tags/ are unchanged. Upstream also adjusted external-engine endpoint descriptions (prose only: the long-polling secret is now documented as providerSecret), which the litchee client already matches. No client code changes 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 Lichess API sync. Bumps the vendored OpenAPI spec submodule (
reference/lichess-api) from572cea5to90055ff.Spec changes detected
Diffing
doc/specs/between the two submodule commits:doc/specs/lichess-api.yaml— API version bump only:2.0.153→2.0.154.doc/specs/schemas/**— unchanged.doc/specs/tags/**— unchanged.The only other upstream changes in the diff are outside
doc/specs/and are documentation/tooling noise:types/lichess-api.d.ts— JSDoc prose only (added blank lines; the external-engine long-polling secret is now described asproviderSecretinstead ofsecretin the human-readable description — no schema field rename).types/package.json,doc/pnpm-lock.yaml,example/oauth-backend/package-lock.json— version/lockfile bumps.Client impact
None. No endpoints, request/response DTO fields, error responses, or enums changed in the source-of-truth spec.
The prose clarification (
secret→providerSecret) for the external-engine "Acquire analysis request" endpoint is already matched by the litchee client:src/api/engine/external_engine.rsserializes{ "providerSecret": ... }and exposesprovider_secreton the registration DTO. No hardcoded API version exists in the crate, so nothing there needs updating either.This PR therefore only advances the vendored spec pointer to keep it current; no
src/api/**changes were required.Verification
Run in the project toolchain — all green:
cargo fmt --check✅cargo clippy --all-targets --all-features -- -D warnings✅cargo test✅ (all unit, integration, and doc tests pass)Generated by Claude Code