Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@effect/ai-anthropic@0.26.1

Patch Changes

• #6288 cfa2bbf Thanks @davidgoli! - populate cachedInputTokens in streaming responses from cache_read_input_tokens

• Updated dependencies [307d54a, d95868a, 95c7d2e, d24511f, 99d5575]:

  • effect@3.21.5
  • @effect/platform@0.96.3

@effect/ai-openai@0.40.2

Patch Changes

• #6297 3e59443 Thanks @shtse8! - Map the OpenAI Responses max_output_tokens finish reason to length instead of falling through to unknown.

• Updated dependencies [307d54a, d95868a, 95c7d2e, d24511f, 99d5575]:

  • effect@3.21.5
  • @effect/platform@0.96.3

effect@3.21.5

Patch Changes

• #6302 307d54a Thanks @fubhy! - Allow cron fields like 5/15 to expand from the starting value through the field maximum.

• #6303 d95868a Thanks @fubhy! - Fix Schedule.cron when the test clock is adjusted to infinity.

• #6285 95c7d2e Thanks @chatman-media! - Fix Cron.next skipping earlier matching days when the upcoming day-of-month does not exist in the current month. For an expression like 0 0 1,16,31 * *, advancing from a date past the 16th selected day 31; in a month without 31 days this overflowed into the following month and landed on a later matching day (e.g. the 16th), silently skipping the 1st. Cron.next now wraps to the first matching day of the next month in that case, matching the behaviour of Cron.prev and other cron implementations.

• #6305 d24511f Thanks @fubhy! - Fix cron parsing and scheduling edge cases for whitespace, Sunday 7, strict numeric tokens, explicit full day ranges, and month-constrained day-of-month / weekday matching.

@effect/platform@0.96.3

Patch Changes

• #6244 99d5575 Thanks @spokodev! - Fix HttpLayerRouter.addHttpApi so two registered APIs no longer share error encoders. Previously each call's middleware was added to a shared context map and applied to every route, so a 500 response from one API was sometimes encoded against the other API's error schema. The fix scopes each API's middleware to its own endpoints (matched by method + path) and wraps each route handler directly.

• Updated dependencies [307d54a, d95868a, 95c7d2e, d24511f]:

  • effect@3.21.5