v43.0.0
GitHub releaseSource-backed
Why it matters: First release after 21 quiet days.
Major Changes · 010a83b: Build the package with Hardhat 3, keeping the exported addresses, ABIs, bytecode and chain data unchanged: · Publish the package as both an ES module and CommonJS · Drop import api3 from '@ api3/contracts' in ES modules in favor of named imports or import… Show allShow less
- Major Changes
- 010a83b: Build the package with Hardhat 3, keeping the exported addresses, ABIs, bytecode and chain data unchanged:
- Publish the package as both an ES module and CommonJS
- Drop import api3 from '@
api3/contracts' in ES modules in favor of named imports or import - as api3 from '@
api3/contracts' - Add an exports map that limits imports to the package root, package.json and the Solidity directories, so deep imports into dist no longer resolve
- Move the api3-contracts CLI from dist/bin/cli.js to dist/cjs/bin/cli.js
- Stop shipping dist/data/*.json and…
Record ship:b2d15394… · 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: “v43.0.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 @api3/contracts@
43.0.0). - 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-11-09 14:29 UTC; HEY first knew on 2026-11-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.