Skip to content

Publish API docs on push to main - #6787

Merged
aleksandar-apostolov merged 3 commits into
developfrom
aleksandarapostolov/and-1617-move-dokka-api-docs-publishing-out-of-the-release-workflow
Oct 7, 2026
Merged

aleksandar-apostolov merged 3 commits into
developfrom
aleksandarapostolov/and-1617-move-dokka-api-docs-publishing-out-of-the-release-workflow

Conversation

@aleksandar-apostolov

@aleksandar-apostolov aleksandar-apostolov commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Goal

Refs AND-1617 — move API-docs publishing to a push-to-main workflow, ahead of dropping it from the release job.

Implementation

New publish-api-docs.yml calls the shared workflow at build-conventions v1.0.1 (d275481) on push to main (+ workflow_dispatch, main only) and passes SLACK_WEBHOOK_ANDROID_CICD for failure alerts.

release.yml stays pinned at 9ea4d20: bumping it pulls in the Stream-repo publishing cutover, which goes in its own PR. Until then the release job still runs Dokka, so docs publish twice per release (same content). The release-time saving lands with that bump.

Testing

actionlint clean. Build-conventions v1.0.1 released through the same path: API Docs ran on the main push and redeployed Pages. After the next release here, it updates getstream.github.io/stream-chat-android.

Adds a caller for the shared publish-api-docs workflow so docs no longer
depend on the release job. The release.yml pin is unchanged; until it is
bumped, docs are published by both.
@aleksandar-apostolov
aleksandar-apostolov requested a review from a team as a code owner October 7, 2026 12:06
@aleksandar-apostolov aleksandar-apostolov added the pr:ci CI changes label Oct 7, 2026
@github-actions

github-actions Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

PR checklist ✅

All required conditions are satisfied:

  • Title length is OK (or ignored by label).
  • At least one pr: label exists.
  • Sections ### Goal, ### Implementation, and ### Testing are filled, or the PR is bot-authored.
  • An issue is linked (Linear ticket or GitHub issue), or the PR is bot-authored.

🎉 Great job! This PR is ready for review.

@github-actions

github-actions Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

SDK Size Comparison 📏

SDK Before After Difference Status
stream-chat-android-client 6.20 MB 6.20 MB 0.00 MB 🟢
stream-chat-android-ui-components 11.51 MB 11.51 MB 0.00 MB 🟢
stream-chat-android-compose 13.18 MB 13.18 MB 0.00 MB 🟢

@coderabbitai

coderabbitai Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Repository UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 291c8455-cc9e-4725-83fe-3d836646fb40
📥 Commits

Reviewing files that changed from the base of the PR and between 3de78e4 and 0963efc.

📒 Files selected for processing (1)
  • .github/workflows/publish-api-docs.yml

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.


Walkthrough

Adds a GitHub Actions workflow that runs on pushes to main or manual dispatch. Its docs job calls a pinned API-docs reusable workflow and receives contents: write permission.

Changes

API Docs Publishing

Layer / File(s) Summary
Configure API docs publishing
.github/workflows/publish-api-docs.yml
Adds push and manual triggers. The docs job calls the pinned reusable workflow with contents: write permission.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Feature

Suggested reviewers: andremion

Merge Risk: ⚪ Minimal · up to 0963e

Pushes to main and manual dispatch invoke the pinned API-docs publisher. No concrete merge-blocking risk is established.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly and concisely describes the new workflow that publishes API docs when changes reach main.
Description check ✅ Passed The description explains the goal, implementation, and testing. The UI, checklist, reviewer checklist, and GIF sections are omitted; the UI and GIF sections do not appear relevant to this workflow cha…
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

A rabbit checks the docs at dawn
A workflow hops and carries on
When main receives a fresh new change
The docs job runs along its range
A manual start can join the play
Then API docs find their way

Comment @coderabbitai help to get the list of available commands.

@sonarqubecloud

sonarqubecloud Bot commented Oct 7, 2026

Copy link
Copy Markdown

@aleksandar-apostolov
aleksandar-apostolov added this pull request to the merge queue Oct 7, 2026
Merged via the queue into develop with commit 0edb219 Oct 7, 2026
20 checks passed
@aleksandar-apostolov
aleksandar-apostolov deleted the aleksandarapostolov/and-1617-move-dokka-api-docs-publishing-out-of-the-release-workflow branch October 7, 2026 14:29
@stream-public-bot stream-public-bot added the released Included in a release label Oct 8, 2026
@stream-public-bot

Copy link
Copy Markdown
Contributor

🚀 Available in v7.14.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr:ci CI changes released Included in a release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants