• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

ilpanich / axiam-typescript-sdk / 32733273863
94%

Build:
DEFAULT BRANCH: main
Ran 24 Aug 2026 01:33PM UTC
Jobs 1
Files 53
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

24 Aug 2026 01:32PM UTC coverage: 93.97%. Remained the same
32733273863

push

github

web-flow
feat(ci): raise the Node floor to 22 and build the newest line (#77)

Three declarations of "which Node does this SDK support" disagreed at once:

  engines.node   >=18   (EOL 2025-04-30)
  @types/node    ^26
  CI matrix      22     (single leg)

So tsc validated the SDK against Node 26 APIs that no tested runtime
provided, while the package advertised installation on a runtime nothing had
ever built. Neither half fails on its own.

- engines.node >=18 -> >=22, the oldest line still receiving security fixes
  (20 went EOL 2026-04-30). No code change accompanies it; the bundle still
  targets ES2022. The SDK was never built or tested on 18, so this corrects a
  declaration that had stopped being true rather than dropping a working
  runtime.
- Gate on floor + newest (22, 26). build, typecheck, the suite and the CJS
  smoke tests run on both; the runtime-independent gates (bundle-grep, the
  token-leak and TLS-lint greps, npm audit, docs, publish dry-run) run once on
  the floor, mirroring the Rust SDK's `if: matrix.toolchain == 'stable'`.
- Add test/core/versionPolicy.test.ts, which fails when the three
  declarations disagree. It goes red against main's configuration.
- Add examples/version-compatibility.ts, a startup preflight reading the
  range from the SDK's own package.json. engines is advisory to npm and
  ignored under engine-strict=false; this makes it assertable.
- Export "./package.json" so that read is possible. Additive.
- Document both claims separately in the README.

Regenerating the lockfile for the engines bump also picked up a pre-existing
drift: the @axiam/opaque-wasm peer dependency was in package.json but missing
from package-lock.json.

Local run on Node 22: 75 test files, 934 passed / 3 skipped. Coverage
95.84% statements, 90.22% branches, 98% functions, 96.54% lines — all above
the configured gates and unchanged by this PR. tsc --noEmit clean.


Claude-Session: https://claude.ai/code/session_01LiZFb1NB813W3BsKArap87

Co-authore... (continued)

1366 of 1514 branches covered (90.22%)

Branch coverage included in aggregate %.

2125 of 2201 relevant lines covered (96.55%)

85.14 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32733273863.1 24 Aug 2026 01:33PM UTC 53
93.97
GitHub Action Run
Source Files on build 32733273863
  • Tree
  • List 53
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #32733273863
  • 2aa374fe on github
  • Prev Build on main (#32723861736)
  • Next Build on main (#32765163364)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc