Skip to content

Releases: xp-forge/lambda-ws

4.0.0: Amazon Linux 2023

Choose a tag to compare

@thekid thekid released this 14 Feb 20:29
  • Made compatible with xp-forge/lambda version 7.0, which uses AL2023
    instead of AL2, which has an EOL date of June 2026. Dropped support
    for version 5.0 of this library at the same time.
    (@thekid)
  • Added PHP 8.6 to the test matrix - @thekid

3.0.0: Drop PHP 7.4

Choose a tag to compare

@thekid thekid released this 14 Feb 20:29

2.3.0: Dispatching

Choose a tag to compare

@thekid thekid released this 20 May 10:40

2.2.0: XP 12 compatibility

Choose a tag to compare

@thekid thekid released this 20 May 10:40
  • Made compatible with XP 12 - @thekid

2.1.0: Application initialization

Choose a tag to compare

@thekid thekid released this 30 Jan 19:06

2.0.0: Response streaming

Choose a tag to compare

@thekid thekid released this 20 Nov 20:12
  • Heads up: Dropped support for XP <= 9, see xp-framework/rfc#341
    (@thekid)
  • Heads up: Bumped minimum version requirement for xp-forge/web
    to version 3.0.0
    (@thekid)
  • Merged PR #10: Implement HTTP response streaming. This bumps the
    minimum version requirement for xp-forge/lambda to version 5.0.0
    (@thekid)

1.3.0: Run HTTP APIs locally

Choose a tag to compare

@thekid thekid released this 20 Nov 19:06

1.2.0: Forward compatibility

Choose a tag to compare

@thekid thekid released this 15 Oct 11:45
  • Made this library compatible with xp-forge/lambda 5.0.0 - @thekid
  • Added PHP 8.4 to the test matrix - @thekid

1.1.4: Streaming fix

Choose a tag to compare

@thekid thekid released this 03 Apr 20:18
  • Fixed case with the string "null" being sent back when using streaming
    and never writing to the response stream by removing response body
    (@thekid)
  • Merged PR #9: Migrate to new testing library - @thekid

1.1.3: Content-Encoding fix

Choose a tag to compare

@thekid thekid released this 14 Sep 19:21
  • Fixed responses with Content-Encoding: gzip (or br) not being
    base64-encoded. This leads to unparseable lambda responses.
    (@thekid)