Release channels
How developer release and changelog sources are published.
Glyph keeps developer release history in the public repositories for the Connect SDK, Relay, and Wallet protocol. This section links to those sources directly rather than copying release notes into the docs.
What the feed shows
The changelog requests up to three published GitHub Releases for each developer-facing project. Release titles, tags, dates, pre-release markers, and notes come directly from GitHub. Draft releases are not displayed.
A project can be active without having a published release or tag. In that case, the feed shows an empty state instead of turning commits or planned work into release notes.
Stable and pre-release work
A release without the pre-release marker is the normal published channel. GitHub releases marked as pre-release remain visible and are labeled as such. Use the release link for the exact assets, compatibility notes, and install guidance for a project.
Live refresh and limits
The changelog is part of the static Waku site, but its release data is fetched in the browser after hydration. Opening or reloading the page checks the public GitHub REST API again. The feed makes one request per project and uses no token or other secret.
GitHub documents a default limit of 60 unauthenticated API requests per hour per IP address. If that limit is reached, or GitHub is unavailable, the affected project keeps its repository and release links and shows a short unavailable state. The page never substitutes made-up release data.
Project sources
Static deployment note
Because the feed refreshes client-side, the deployed site must serve JavaScript and allow browser requests to https://api.github.com. A strict Content Security Policy should include that host in connect-src. The page itself still renders its explanatory text and source links when the API cannot be reached.