main #1

Merged
ferociousbyte merged 2 commits from main into stable 2026-10-25 21:00:16 +00:00
No description provided.
A push to stable releases the next YYYY.M.N and tags it, other pushes build CI versions only
All checks were successful
/ build-and-pack (push) Successful in 40s
d380381b04
The release no longer comes from a tag pushed by hand: ci-version.sh gives "stable" the next version of this
repository's own tags (YYYY.M.(N+1), or YYYY.M.0 in a new month), the packages go into both feeds, and CI tags the
commit once they are pushed. A commit that carries a release tag already isn't released again; workflow_dispatch runs
a failed release once more. main and every other branch build prereleases into code.talaryon.dev as before, and tags
start no build. The legacy client/ tags no longer count: the plain ones are past them.

The client checks its packages for known vulnerabilities too, like the server and the storage service. The script is
the same file in all three repositories.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The storage service's URLs expire, so pages, Markdown and meta tags need an address that doesn't. The new package maps
one (MapUnilayerAssets): it asks the API for the download URL, redirects there and lets the browser keep the redirect,
refuses modifiers the site doesn't allow, and writes its links (UnilayerAssetUrls).

The client hands out a download order again for DownloadUrlCacheSeconds without asking the API, shared by the clients
of a name, never in the order's last minute. Off by default: the cache is shared by every caller of a name.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
unilayer/client!1
No description provided.