v5.1.0
GitHub releaseSource-backed
Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.
fix: agent-trading work order phase 3 (standalone perp tools, update_order/transfer encoding, Node 22, artifact CI, session refresh) by @kingassune Show allShow less
- What's Changed
- fix: agent-trading work order phase 3 (standalone perp tools, update_order/transfer encoding, Node 22, artifact CI, session refresh) by @kingassune in https://github.com/GemachDAO/gdex-skill/pull/63 Full Changelog: https://github.com/GemachDAO/gdex-skill/compare/v5.0.0...v5.1.0
Record ship:06df7588… · 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: “v5.1.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 @gemachdao/gdex-mcp-server@
5.1.0); a package version published from the same repository matches it (npm @gemachdao/gdex-skill@ 5.1.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-10-19 22:48 UTC; HEY first knew on 2026-10-19.
- 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.