Skip to content

Releases: HarperFast/integration-testing

v1.0.3

Choose a tag to compare

@github-actions github-actions released this 08 Oct 20:54

1.0.3 (2026-10-08)

Bug Fixes

  • collapse repeated log lines in the failure log tail (#36) (8f0a619)

v1.0.2

Choose a tag to compare

@github-actions github-actions released this 08 Oct 20:15

1.0.2 (2026-10-08)

Bug Fixes

  • make loopback pool file writes atomic and reads torn-write tolerant (#32) (a734985)

v1.0.1

Choose a tag to compare

@github-actions github-actions released this 06 Oct 18:16

1.0.1 (2026-10-06)

Bug Fixes

  • lifecycle: unpublish an install directory an allocation failure removed (456d9ed)
  • loopback: explain an address that could not be checked, and keep the allocation error (5b03941), closes #38
  • loopback: read a probe failure's reason without assuming an Error (d73dbab)
  • loopback: refuse an address that another process's listener on all interfaces covers (2fbdb10), closes #38
  • loopback: skip the probe on Linux, and let an accepting port win over an uncheckable one (53688f4)
  • loopback: treat an unanswered probe as uncheckable, and clean up a refused fixture install (77e53a5)

Documentation

  • lifecycle: document launchHarper's parameters and what it reuses (a3a1eca)
  • loopback: trim added comments to the constraints they carry (8ba639c)
  • loopback: Windows shares the macOS exposure, per CI (77d7f45)

Tests

  • loopback: skip the probe-failure cases as one suite, before any setup (3328dc3)
  • loopback: skip the stalled-handshake cases where the OS resets past a full backlog (ecd9592)

v1.0.0

Choose a tag to compare

@github-actions github-actions released this 03 Sep 21:57

1.0.0 (2026-09-03)

⚠ BREAKING CHANGES

  • a call that passes the node where the context belongs now throws
    a TypeError instead of being silently accepted. Any suite doing that today passes
    while leaking a Harper instance, and will go red on upgrade — the point of the
    change, but it is a visible behavior change, so it is released as a major rather
    than slipped into a patch. Consumers on a ^0.7.x range opt in deliberately.

Bug Fixes

  • reject a Harper node where a test context is expected (#31) (8854fc8)

v0.7.1

Choose a tag to compare

@github-actions github-actions released this 27 Jul 17:21

0.7.1 (2026-07-27)

Bug Fixes

  • release: align release-note sections with studio (6c6ad3d)

v0.7.0

Choose a tag to compare

@github-actions github-actions released this 22 Jul 23:57

0.7.0 (2026-07-22)

Features

  • startup: log the resolved Harper binary and warn on node_modules/dist ambiguity (aacdfca)
  • startup: walk ancestors for the local-build warning (review) (154cba3)

Bug Fixes

  • setup-loopback: announce the range up front; capture ifconfig output once (c17d928)
  • setup-loopback: verify aliases landed before reporting success (cb4fc98)

v0.6.4

Choose a tag to compare

@github-actions github-actions released this 17 Jul 20:09

0.6.4 (2026-07-17)

Bug Fixes

  • startup: scale the idle-silence timeout for CI, matching the absolute-max ceiling (#22) (ab75e40)

v0.6.3

Choose a tag to compare

@github-actions github-actions released this 13 Jul 18:32

0.6.3 (2026-07-13)

Bug Fixes

  • use /32 host netmask for loopback aliases to stop mDNSResponder storm (96bde9b)

v0.6.2

Choose a tag to compare

@github-actions github-actions released this 20 Jun 22:17

0.6.2 (2026-06-20)

Documentation

  • loopback: note HTTP-port canary detection is Linux-effective (macOS caveat) (5675699)

Bug Fixes

  • loopback: conflict canary also probes the HTTP port to catch lingering workers (716d67c), closes harper#1427

v0.6.1

Choose a tag to compare

@github-actions github-actions released this 17 Jun 18:30

0.6.1 (2026-06-17)

Bug Fixes

  • Commit package-lock update when bumping version too (95d8eca)