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/cli@0.36.26

Patch Changes

• Updated dependencies [ee08593, da6d7d8]:
  • @effect/schema@0.67.4
  • @effect/platform@0.53.7

@effect/experimental@0.16.7

Patch Changes

• Updated dependencies [ee08593, da6d7d8]:
  • @effect/schema@0.67.4
  • @effect/platform@0.53.7
  • @effect/platform-node@0.49.7

@effect/platform@0.53.7

Patch Changes

• Updated dependencies [ee08593, da6d7d8]:
  • @effect/schema@0.67.4

@effect/platform-browser@0.33.22

Patch Changes

• #2691 dc06f27 Thanks @KhraksMamtsov! - add Geolocation module to @effect/platform-browser

• Updated dependencies []:

  • @effect/platform@0.53.7

@effect/platform-bun@0.34.13

Patch Changes

• Updated dependencies []:
  • @effect/platform@0.53.7
  • @effect/platform-node-shared@0.4.26

@effect/platform-node@0.49.7

Patch Changes

• Updated dependencies []:
  • @effect/platform@0.53.7
  • @effect/platform-node-shared@0.4.26

@effect/platform-node-shared@0.4.26

Patch Changes

• Updated dependencies []:
  • @effect/platform@0.53.7

@effect/rpc@0.30.26

Patch Changes

• Updated dependencies [ee08593, da6d7d8]:
  • @effect/schema@0.67.4
  • @effect/platform@0.53.7

@effect/rpc-http@0.28.26

Patch Changes

• Updated dependencies [ee08593, da6d7d8]:
  • @effect/schema@0.67.4
  • @effect/platform@0.53.7
  • @effect/rpc@0.30.26

@effect/schema@0.67.4

Patch Changes

• #2756 ee08593 Thanks @gcanti! - Improving Predicate Usability of Schema.is

  Before this update, the Schema.is(mySchema) function couldn't be easily used as a predicate or refinement in common array methods like filter or find. This was because the function's signature was:

  (value: unknown, overrideOptions?: AST.ParseOptions) => value is A

  Meanwhile, the function expected by methods like filter has the following signature:

  (value: unknown, index: number) => value is A

  To make Schema.is compatible with these array methods, we've adjusted the function's signature to accept number as a possible value for the second parameter, in which case it is ignored:

  -(value: unknown, overrideOptions?: AST.ParseOptions) => value is A
  +(value: unknown, overrideOptions?: AST.ParseOptions | number) => value is A

  Here's a practical example comparing the behavior before and after the change:

  Before:

  import { Schema } from "@effect/schema";
  
  declare const array: Array<string | number>;
  
  /*
  Throws an error:
  No overload matches this call.
  ...
  Types of parameters 'overrideOptions' and 'index' are incompatible.
  */
  const strings = array.filter(Schema.is(Schema.String));

  Now:

  import { Schema } from "@effect/schema";
  
  declare const array: Array<string | number>;
  
  // const strings: string[]
  const strings = array.filter(Schema.is(Schema.String));

  Note that the result has been correctly narrowed to string[].

• #2746 da6d7d8 Thanks @gcanti! - pick: do not return a ComposeTransformation if none of the picked keys are related to a property signature transformation, closes Schema.optional struct prop restricts possible schema operations #2743

@effect/sql@0.2.9

Patch Changes

• #2712 01b4553 Thanks @vecerek! - Use constants from @opentelemetry/semantic-conventions as span attribute names instead of hard-coded values

• Updated dependencies [ee08593, da6d7d8]:

  • @effect/schema@0.67.4
  • @effect/platform@0.53.7

@effect/sql-mssql@0.2.9

Patch Changes

• #2712 01b4553 Thanks @vecerek! - Use constants from @opentelemetry/semantic-conventions as span attribute names instead of hard-coded values

• Updated dependencies [01b4553]:

  • @effect/sql@0.2.9
  • @effect/platform@0.53.7

@effect/sql-mysql2@0.2.9

Patch Changes

• #2712 01b4553 Thanks @vecerek! - Use constants from @opentelemetry/semantic-conventions as span attribute names instead of hard-coded values

• Updated dependencies [01b4553]:

  • @effect/sql@0.2.9
  • @effect/platform@0.53.7

@effect/sql-pg@0.2.9

Patch Changes

• #2712 01b4553 Thanks @vecerek! - Use constants from @opentelemetry/semantic-conventions as span attribute names instead of hard-coded values

• Updated dependencies [01b4553]:

  • @effect/sql@0.2.9
  • @effect/platform@0.53.7

@effect/sql-sqlite-bun@0.2.9

Patch Changes

• #2712 01b4553 Thanks @vecerek! - Use constants from @opentelemetry/semantic-conventions as span attribute names instead of hard-coded values

• Updated dependencies [01b4553]:

  • @effect/sql@0.2.9
  • @effect/platform@0.53.7

@effect/sql-sqlite-node@0.2.10

Patch Changes

• #2712 01b4553 Thanks @vecerek! - Use constants from @opentelemetry/semantic-conventions as span attribute names instead of hard-coded values

• Updated dependencies [01b4553]:

  • @effect/sql@0.2.9
  • @effect/platform@0.53.7

@effect/sql-sqlite-react-native@0.3.9

Patch Changes

• #2712 01b4553 Thanks @vecerek! - Use constants from @opentelemetry/semantic-conventions as span attribute names instead of hard-coded values

• Updated dependencies [01b4553]:

  • @effect/sql@0.2.9

@effect/sql-sqlite-wasm@0.2.9

Patch Changes

• #2712 01b4553 Thanks @vecerek! - Use constants from @opentelemetry/semantic-conventions as span attribute names instead of hard-coded values

• Updated dependencies [01b4553]:

  • @effect/sql@0.2.9