chore: split CD workflow into separate pipelines for client and server#92
Merged
Conversation
Joszkooo
requested changes
Jun 25, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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?)
pathsproperty)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):


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