Skip to content

Conversation

@gpunto
Copy link
Collaborator

@gpunto gpunto commented Nov 11, 2025

Adding automatic snapshot publishing on commits on develop, like we do it in Chat and Video. It's also a good opportunity to test this workflow here before changing Chat and Video to use the common one in this repository.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds automatic snapshot publishing triggered on pushes to the develop branch while simplifying the manual release workflow by removing snapshot-specific input parameters.

  • Creates a new automatic snapshot workflow that triggers on pushes to develop
  • Removes snapshot, version-properties-file inputs from the manual publish workflow
  • Separates snapshot publishing from manual version releases

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
.github/workflows/publish-snapshot.yml New workflow for automatic snapshot builds triggered on develop branch pushes
.github/workflows/publish-new-version.yml Removes snapshot-related inputs, focusing on manual version releases only

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@gpunto gpunto force-pushed the publish-snapshots-on-develop branch from 8fbc6ac to e0b934d Compare November 11, 2025 09:54
@gpunto gpunto requested a review from Copilot November 11, 2025 09:54
@gpunto gpunto marked this pull request as ready for review November 11, 2025 09:56
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

push: false

- name: Push changes to ci-release branch
if: ${{ !inputs.snapshot }}
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Took the opportunity to completely split snapshot and final release publishing. I think it's less error prone this way, as we now have two separate jobs instead of one job with excluded steps.

I also considered splitting the workflow into two files, but discarded that approach because I find it clearer to see the publishing in one place, so you don't have to know that two workflows exist.

- minor
- major
default: minor
version-properties-file:
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We just rely on the defaults (also, the idea is to align all SDKs to use the same mechanisms, so nobody will have to specify the version properties file).

@gpunto gpunto requested a review from a team November 11, 2025 14:53
Copy link

@VelikovPetar VelikovPetar left a comment

Choose a reason for hiding this comment

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

LGTM!
Probably would be good to have an approval from someone from video as well!

@aleksandar-apostolov aleksandar-apostolov merged commit 336d3fa into develop Nov 24, 2025
9 checks passed
@aleksandar-apostolov aleksandar-apostolov deleted the publish-snapshots-on-develop branch November 24, 2025 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants