Skip to content

Disable automatic snapshot publishing on develop pushes - #1858

Merged
aleksandar-apostolov merged 1 commit into
developfrom
ci/disable-auto-snapshot-publish
Sep 30, 2026
Merged

aleksandar-apostolov merged 1 commit into
developfrom
ci/disable-auto-snapshot-publish

Conversation

@gpunto

@gpunto gpunto commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Goal

Stop publishing a snapshot on every push to develop. Snapshots can still be published by running the workflow manually.

Closes AND-1581

Implementation

  • Remove the push trigger from publish-snapshot.yml, keeping workflow_dispatch.

Testing

None needed, CI config only.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Snapshot publishing now runs only when manually triggered; updates to the development branch no longer start it automatically. This changes when snapshot builds are published, while leaving the application’s features unchanged.

@gpunto gpunto added the pr:ci CI / GitHub Actions / workflow updates label Sep 30, 2026
@github-actions

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

Copy link
Copy Markdown
Contributor

SDK Size Comparison 📏

SDK Before After Difference Status
stream-video-android-core 12.38 MB 12.38 MB 0.00 MB 🟢
stream-video-android-ui-xml 5.66 MB 5.66 MB 0.00 MB 🟢
stream-video-android-ui-compose 6.19 MB 6.19 MB 0.00 MB 🟢

@gpunto
gpunto marked this pull request as ready for review September 30, 2026 10:48
@gpunto
gpunto requested a review from a team as a code owner September 30, 2026 10:48
@sonarqubecloud

Copy link
Copy Markdown

@coderabbitai

coderabbitai Bot commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

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: 58a0fda3-a767-44c8-aeae-2ff0ca6b554e

📥 Commits

Reviewing files that changed from the base of the PR and between 4da50b2 and d768ea2.

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

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


Walkthrough

The snapshot publishing workflow no longer runs on pushes to develop. It runs only when manually dispatched.

Changes

Snapshot publishing

Layer / File(s) Summary
Snapshot workflow trigger
.github/workflows/publish-snapshot.yml
The workflow documents manual snapshot publishing and removes the push trigger for develop. Manual dispatch remains enabled.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Suggested reviewers: rahul-lohra

Merge Risk: ⚪ Minimal · up to d768e

Snapshots will no longer publish automatically on pushes to develop, while manual publishing remains available. No actionable merge risk is evident.

Architecture Summary

Architecture risk: 🔵 Low · up to d768e

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

  • observed — Modified behavior in .github/workflows/publish-snapshot.yml: The workflow now documents that snapshots are published manually and removes the push trigger for develop; workflow_dispatch remains the trigger.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: disabling automatic snapshot publishing on pushes to develop.
Description check ✅ Passed The description includes the goal, implementation, testing information, and linked issue. The omitted UI, checklist, reviewer, and GIF sections are not relevant to this CI configuration change.
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

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 snapshot switch,
No push can start it with a twitch.
A manual call begins the run,
The workflow waits until it's done.
Then hops away beneath the moon.

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

@aleksandar-apostolov aleksandar-apostolov left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@aleksandar-apostolov
aleksandar-apostolov merged commit d7fdaff into develop Sep 30, 2026
18 of 19 checks passed
@aleksandar-apostolov
aleksandar-apostolov deleted the ci/disable-auto-snapshot-publish branch September 30, 2026 10:53
@stream-public-bot stream-public-bot added the released Included in a release label Oct 7, 2026
@stream-public-bot

Copy link
Copy Markdown
Collaborator

🚀 Available in v1.36.0

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

Labels

pr:ci CI / GitHub Actions / workflow updates released Included in a release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants