Skip to content

chore: split CD workflow into separate pipelines for client and server#92

Merged
Aleks334 merged 1 commit into
mainfrom
split-cd-workflows
Jun 25, 2026
Merged

chore: split CD workflow into separate pipelines for client and server#92
Aleks334 merged 1 commit into
mainfrom
split-cd-workflows

Conversation

@Aleks334

@Aleks334 Aleks334 commented Jun 19, 2026

Copy link
Copy Markdown
Member

Changes

the main reason why I created this PR is that currently we use only one tag for both server and client releases. Now bumping only server and then both will create inconsistent git tags.

For example:
v0.1.1 (both server and client) -> v0.1.2 (only server) -> v0.1.3 (both server and client).

What happened with v0.1.2 for client? In GHCR it doesn't exists (that's okay - it wasn't released) but git tag v0.1.2 is present. This is confusing a lot.

After this change we not only fix this issue but also are able to completely independently deploy server and client (without it we'd had the one tag for both - another problem, how to deploy this separately or rollback only client?)

  • split contents of CD workflow for both client and server into separate workflows to release them independently
  • separate git tags and github releases for client and server (with prefixes: client-v and server-v). For example client-v0.1.2 and server-v0.1.1. They are not semver compatible but it's not public library so that shouldn't be an issue
  • prevent changes only to .md files being released (paths property)
  • both new CD workflows for client and server run on merge to main and optionally manually (only for emergency situations)

How to test (optional)

See my fork or create your own (releases, tags, packages): https://github.com/Aleks334/put-wiki. I created release for both, only server and for both again. At the end I merged changes related only to .md file to check if that would cause pipeline to run

Screenshots / recordings (for UI stuff)

GHCR packages (I don't know if you will see them due to permissions):
image
image

Checklist

  • PR is linked to an issue (tab on the right).
  • Acceptance criteria (from issue) are met.
  • All status checks (CI) are green.
  • Tests added / updated.
  • Docs updated (if applicable).

To have your PR reviewed put the link e.g. https://github.com/akai-org/put-wiki/pull/0 to the Review PR thread on put-wiki dc channel (you must be member of the AKAI discord server)

Comment thread .github/workflows/cd-client.yml Dismissed
Comment thread .github/workflows/cd-client.yml Dismissed
Comment thread .github/workflows/cd-client.yml Dismissed
Comment thread .github/workflows/cd-client.yml Dismissed
Comment thread .github/workflows/cd-client.yml Dismissed
Comment thread .github/workflows/cd-server.yml Dismissed
Comment thread .github/workflows/cd-server.yml Dismissed
Comment thread .github/workflows/cd-server.yml Dismissed
Comment thread .github/workflows/cd-server.yml Dismissed
Comment thread .github/workflows/cd-server.yml Dismissed
@Aleks334 Aleks334 changed the title WIP: split CD workflow into separate pipelines for client and server chore: split CD workflow into separate pipelines for client and server Jun 19, 2026
Comment thread .github/workflows/cd-client.yml

@Joszkooo Joszkooo left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM

@Aleks334 Aleks334 merged commit 6fe241c into main Jun 25, 2026
8 checks passed
@Aleks334 Aleks334 deleted the split-cd-workflows branch June 25, 2026 09:27
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.

3 participants