Phosphor 0.11.5
GitHub releaseSource-backed
Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.
Phosphor 0.11.5 for Mac (Apple silicon) 0.11.5: a resting entry is never ended on a restart while it is still on the book Install. Open the DMG, drag Phosphor into Applications, open it from there. Verify the download before opening it. In Terminal: cd ~/Downloads && shasum -a… Show allShow less
Phosphor 0.11.5 for Mac (Apple silicon) 0.11.5: a resting entry is never ended on a restart while it is still on the book Install. Open the DMG, drag Phosphor into Applications, open it from there. Verify the download before opening it. In Terminal: cd ~/Downloads && shasum -a 256 Phosphor-macOS-arm64.dmg It must print exactly: b80a3f145821302dc5c9cd9a5037e90070930e61131bad9f3d6b580a2a0ea11f Phosphor-macOS-arm64.dmg The update archive, the file installed copies download, has its own line. To check it, download it from this page too, then: cd ~/Downloads &&…
Record ship:8e9add59… · 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: “Phosphor 0.11.5” (v0.11.5).
- 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 (HEY holds the first 600 characters of it). 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-10-09 22:39 UTC; HEY first knew on 2026-10-09.
- 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 (HEY holds the first 600 characters of it). 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.