v2.5.0
GitHub releaseSource-backed
Why it matters: First release after 170 quiet days.
2.5.0 (2026-09-16) Features · chains: add Robinhood Chain mainnet and USDG (#116) (1e9d910) --- npm: @eco-foundation/chains@ 2.5.0 is staged, not yet published. A maintainer promotes it with npm stage approve (2FA). Until then npm install cannot resolve this version. Show allShow less
- 2.5.0 (2026-09-16) Features
- chains: add Robinhood Chain mainnet and USDG (#116) (1e9d910) --- npm: @eco-foundation/chains@
2.5.0 is staged, not yet published. A maintainer promotes it with npm stage approve (2FA). Until then npm install cannot resolve this version.
Record ship:965dac9b… · 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: “v2.5.0”.
- 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. Independently recorded: a package version published from the same repository matches it (npm @eco-foundation/chains@
2.5.0). - 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-09-16 21:14 UTC; HEY first knew on 2026-09-30. HEY indexed it later, as history.
- 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.