Repository navigation
release: 0.3.0 - #155
release: 0.3.0#155
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
d5aa522 to
daee3dc
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d5aa5226c1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| run: pnpm build | ||
|
|
||
| - name: Publish to npm | ||
| run: pnpm publish --no-git-checks --provenance --access public --tag next |
There was a problem hiding this comment.
next tag used for this prerelease
This publishes 0.3.0 only under the next dist-tag, while README.md still tells users to run pnpm add equine. The npm dist-tag documentation states that an unqualified install selects latest, so users following the README will receive the previous 0.2.1 client, whose API exports only Equine, and the documented accountMe/setToken imports will fail. Either publish this release under latest or change the installation command to pnpm add equine@next.
Useful? React with 👍 / 👎.
- Bump version to 0.3.0 (first prerelease of the revived client). - README: rewrite the API-reference section so endpoint discovery is actually usable — the Lichess docs are organized by URL path, not function name, so point to editor autocomplete + hover JSDoc, the operationId->name mapping, and src/client/sdk.gen.ts as the function index. - Add .github/workflows/publish.yml: publish to npm on GitHub Release (published), with provenance; needs an NPM_TOKEN secret.
daee3dc to
6dfc3f9
Compare
|
Resolved in |
|
@codex review |
|
Codex Review: Didn't find any major issues. Another round soon, please! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
why?
First tagged prerelease of the revived client, plus two loose ends: the version still read
1.0.0-alpha.0, and the README pointed endpoint discovery at the Lichess docs page (organized by URL path) which does not list the generated function names.how?
0.3.0(prerelease line).operationId; discover them via editor autocomplete + hover JSDoc;src/client/sdk.gen.tsis the full function index..github/workflows/publish.yml— publishes to npm on GitHub Release (published) with provenance (--tag next). Requires anNPM_TOKENsecret.