v0.3.0-rc.58
GitHub releaseSource-backed
Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.
Keep workspace navigation responsive while full account data loads. Earnings and purchases use the buyer snapshot instead of requiring a full workspace reload; the selected page retains its navigation and loading state. Public source: 79f2fff6f04d9c5aaa538f6975909b8e170637b5… Show allShow less
Keep workspace navigation responsive while full account data loads. Earnings and purchases use the buyer snapshot instead of requiring a full workspace reload; the selected page retains its navigation and loading state. Public source: 79f2fff6f04d9c5aaa538f6975909b8e170637b5 Image: ghcr.io/thot-market/thotmarket@
Record ship:ec841754… · HEY counts it as building; it does not judge the release’s quality.
Release, read from the team’s GitHub · no deployment linked
- What it names
- The team’s release names it: “v0.3.0-rc.58”.
- Stage
- A release is code the team published; HEY has not observed it deployed unless a link below says so.
- Reported by
- Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
- Release and deployment
- Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to a deployment.
- Activity
- No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
- When
- The source dates it 2026-11-04 18:48 UTC; HEY first knew on 2026-11-04.
- Not known
- HEY does not hold the commit the release was cut from.
- HEY has not observed a deployment of this change.
- Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to a deployment.
Evidence: ship record
A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.