You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
If only some doc changes are needed, branch from the last release tag, cherry-pick the needed doc changes, and then run `make deploy`.
This will publish the doc sources to the `docs/current` branch. They will be included automatically in the next build for the main docs. A build for the main docs can also be triggered by re-running the last docs build in GitHub workflows (on the `main` branch for dev docs, on the `current` branch for prod docs).
This will publish the doc sources to the `docs/kalix-current` branch. They will be included automatically in the next build for the main docs.
A build for the main docs can also be triggered by re-running the last docs `build-and-publish-[x]` in Circle CI on the `main` branch: