Repository navigation
ci: sync independent client and WebLite releases - #348
Merged
Merged
Conversation
Pin each product version and Release tag separately, retain legacy downloads, and synchronize Core manifests from WEBLITE_VERSION.
LeeEirc
approved these changes
Oct 15, 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
2 participants
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.
Client and WebLite releases are tracked independently through CLIENT_VERSION and WEBLITE_VERSION. Downloads derive client-v and weblite-v tags directly, while installer names and public download aliases stay unchanged.
Dependency checks select complete published releases independently, and Core WebLite manifests synchronize from WEBLITE_VERSION.
Validation: all 6 client version and downloader tests passed; sh -n client.sh and git diff --check passed.