-
Notifications
You must be signed in to change notification settings - Fork 89
Add docs generation workflows #527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the rust sdks update intentional? there's also a crypto update that seems unlikely to be related to docs.
edit: nevermind I see the description mentions the other fixes. please submit them in separate PRs.
sorry, thought I had submitted the review but my review comments were stuck in "pending" :/ |
@rektdeckard since last week most CI workflows were broken. I extracted the bare minimum of necessary fixes in #529. |
565294f
to
d14ba5b
Compare
d14ba5b
to
7688a33
Compare
@lukasIO removed the non-docs changes, and since we are pinning both |
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
contents: read | ||
|
||
on: | ||
workflow_dispatch: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks like triggering publishing of docs is exclusively a manual process.
It would be great if we could automate it as part of the release workflow, i.e. if a package got published, also publish the latest docs, so that the docs are always up to date with the latest release without us having to remember explicitly publishing the docs.
https://linear.app/livekit/issue/DPRO-377/add-nodejs-reference-docs
server-sdk-js
andrtc-node