chore(deps): update all patch dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@changesets/cli (source)	2.27.3 -> 2.27.5
@effect/platform (source)	0.55.0 -> 0.55.5
@effect/platform-node (source)	0.51.0 -> 0.51.5
@effect/schema (source)	0.67.13 -> 0.67.18
effect (source)	3.2.5 -> 3.2.8
pnpm (source)	9.1.1 -> 9.1.4
tsx	4.11.0 -> 4.11.2

---

Release Notes

changesets/changesets (@​changesets/cli)

v2.27.5

Compare Source

Patch Changes

• #​1370 5e9d33a Thanks @​Andarist! - Fixed a regression that caused changeset version to fail on packages having a dev dependency on a skipped package.

• Updated dependencies [5e9d33a]:

  • @​changesets/get-dependents-graph@​2.1.0
  • @​changesets/assemble-release-plan@​6.0.2
  • @​changesets/config@​3.0.1
  • @​changesets/get-release-plan@​4.0.2
  • @​changesets/apply-release-plan@​7.0.3

v2.27.4

Compare Source

Patch Changes

• #​1361 954a16a Thanks @​jakebailey! - Ensure that version/tag do not touch private packages with when versioning/tagging is turned off using versionPackages config

• #​1369 d729d8c Thanks @​Andarist! - changeset tag should now correctly skip tags that exist on the remote

• Updated dependencies [954a16a]:

  • @​changesets/assemble-release-plan@​6.0.1
  • @​changesets/apply-release-plan@​7.0.2
  • @​changesets/get-release-plan@​4.0.1

Effect-TS/effect (@​effect/platform)

v0.55.5

Compare Source

Patch Changes

• Updated dependencies [a0dd1c1]:
  • @​effect/schema@​0.67.18

v0.55.4

Compare Source

Patch Changes

• Updated dependencies [d9d22e7, 3c080f7, 3c080f7, 7d6d875, 70cda70, fb91f17]:
  • @​effect/schema@​0.67.17
  • effect@3.2.8

v0.55.3

Compare Source

Patch Changes

• Updated dependencies [5745886, 6801fca]:
  • @​effect/schema@​0.67.16
  • effect@3.2.7

v0.55.2

Compare Source

Patch Changes

• #​2737 2c2280b Thanks @​jessekelly881! - added KeyValueStore.layerStorage to wrap instances of the Storage type.

• Updated dependencies [e2740fc, cc8ac50, 60fe3d5]:

  • @​effect/schema@​0.67.15
  • effect@3.2.6

v0.55.1

Compare Source

Patch Changes

• Updated dependencies [c5846e9]:
  • @​effect/schema@​0.67.14

Effect-TS/effect (@​effect/platform-node)

v0.51.5

Compare Source

Patch Changes

• Updated dependencies []:
  • @​effect/platform@​0.55.5
  • @​effect/platform-node-shared@​0.6.5

v0.51.4

Compare Source

Patch Changes

• Updated dependencies [fb91f17]:
  • effect@3.2.8
  • @​effect/platform@​0.55.4
  • @​effect/platform-node-shared@​0.6.4

v0.51.3

Compare Source

Patch Changes

• Updated dependencies [6801fca]:
  • effect@3.2.7
  • @​effect/platform@​0.55.3
  • @​effect/platform-node-shared@​0.6.3

v0.51.2

Compare Source

Patch Changes

• Updated dependencies [2c2280b, cc8ac50]:
  • @​effect/platform@​0.55.2
  • effect@3.2.6
  • @​effect/platform-node-shared@​0.6.2

v0.51.1

Compare Source

Patch Changes

• Updated dependencies [c5c94ed]:
  • @​effect/platform-node-shared@​0.6.1
  • @​effect/platform@​0.55.1

Effect-TS/effect (@​effect/schema)

v0.67.18

Compare Source

Patch Changes

• #​2908 a0dd1c1 Thanks @​gcanti! - TemplateLiteral: fix bug related to ${number} span, closes #​2907

v0.67.17

Compare Source

Patch Changes

• #​2892 d9d22e7 Thanks @​gcanti! - Schema

  • add propertySignature API interface (with a from property)
  • extend optional API interface with a from property
  • extend optionalWithOptions API interface with a from property

• #​2901 3c080f7 Thanks @​gcanti! - make the AST.TemplateLiteral constructor public

• #​2901 3c080f7 Thanks @​gcanti! - add support for string literals to Schema.TemplateLiteral and TemplateLiteral API interface.

  Before

  import { Schema } from "@​effect/schema";
  
  // `https://${string}.com` | `https://${string}.net`
  const MyUrl = Schema.TemplateLiteral(
    Schema.Literal("https://"),
    Schema.String,
    Schema.Literal("."),
    Schema.Literal("com", "net"),
  );

  Now

  import { Schema } from "@​effect/schema";
  
  // `https://${string}.com` | `https://${string}.net`
  const MyUrl = Schema.TemplateLiteral(
    "https://",
    Schema.String,
    ".",
    Schema.Literal("com", "net"),
  );

• #​2905 7d6d875 Thanks @​gcanti! - add support for unions to rename, closes #​2904

• #​2897 70cda70 Thanks @​gcanti! - Add encodedBoundSchema API.

  The encodedBoundSchema function is similar to encodedSchema but preserves the refinements up to the first transformation point in the
  original schema.

  Function Signature:

  export const encodedBoundSchema = <A, I, R>(schema: Schema<A, I, R>): Schema<I>

  The term "bound" in this context refers to the boundary up to which refinements are preserved when extracting the encoded form of a schema. It essentially marks the limit to which initial validations and structure are maintained before any transformations are applied.

  Example Usage:

  import { Schema } from "@​effect/schema";
  
  const schema = Schema.Struct({
    foo: Schema.String.pipe(Schema.minLength(3), Schema.compose(Schema.Trim)),
  });
  
  // The resultingEncodedBoundSchema preserves the minLength(3) refinement,
  // ensuring the string length condition is enforced but omits the Trim transformation.
  const resultingEncodedBoundSchema = Schema.encodedBoundSchema(schema);
  
  // resultingEncodedBoundSchema is the same as:
  Schema.Struct({
    foo: Schema.String.pipe(Schema.minLength(3)),
  });

  In the provided example:

  • Initial Schema: The schema for foo includes a refinement to ensure strings have a minimum length of three characters and a transformation to trim the string.
  • Resulting Schema: resultingEncodedBoundSchema maintains the minLength(3) condition, ensuring that this validation persists. However, it excludes the trimming transformation, focusing solely on the length requirement without altering the string's formatting.

• Updated dependencies [fb91f17]:

  • effect@3.2.8

v0.67.16

Compare Source

Patch Changes

• #​2890 5745886 Thanks @​gcanti! - Fix constructor type inference for classes with all optional fields, closes #​2888

  This fix addresses an issue where TypeScript incorrectly inferred the constructor parameter type as an empty object {} when all class fields were optional. Now, the constructor properly recognizes arguments as objects with optional fields (e.g., { abc?: number, xyz?: number }).

• Updated dependencies [6801fca]:

  • effect@3.2.7

v0.67.15

Compare Source

Patch Changes

• #​2882 e2740fc Thanks @​gcanti! - add requiredToOptional function to Schema module, closes #​2881

• #​2880 60fe3d5 Thanks @​gcanti! - add missing makePropertySignature constructor

• Updated dependencies [cc8ac50]:

  • effect@3.2.6

v0.67.14

Compare Source

Patch Changes

• #​2851 c5846e9 Thanks @​gcanti! - Add tag and TaggedStruct constructors.

  In TypeScript tags help to enhance type discrimination and pattern matching by providing a simple yet powerful way to define and recognize different data types.

  What is a Tag?

  A tag is a literal value added to data structures, commonly used in structs, to distinguish between various object types or variants within tagged unions. This literal acts as a discriminator, making it easier to handle and process different types of data correctly and efficiently.

  Using the tag Constructor

  The tag constructor is specifically designed to create a property signature that holds a specific literal value, serving as the discriminator for object types. Here's how you can define a schema with a tag:

  import { Schema } from "@​effect/schema";
  
  const User = Schema.Struct({
    _tag: Schema.tag("User"),
    name: Schema.String,
    age: Schema.Number,
  });
  
  assert.deepStrictEqual(User.make({ name: "John", age: 44 }), {
    _tag: "User",
    name: "John",
    age: 44,
  });

  In the example above, Schema.tag("User") attaches a _tag property to the User struct schema, effectively labeling objects of this struct type as "User". This label is automatically applied when using the make method to create new instances, simplifying object creation and ensuring consistent tagging.

  Simplifying Tagged Structs with TaggedStruct

  The TaggedStruct constructor streamlines the process of creating tagged structs by directly integrating the tag into the struct definition. This method provides a clearer and more declarative approach to building data structures with embedded discriminators.

  import { Schema } from "@​effect/schema";
  
  const User = Schema.TaggedStruct("User", {
    name: Schema.String,
    age: Schema.Number,
  });
  
  // `_tag` is optional
  const userInstance = User.make({ name: "John", age: 44 });
  
  assert.deepStrictEqual(userInstance, {
    _tag: "User",
    name: "John",
    age: 44,
  });

  Multiple Tags

  While a primary tag is often sufficient, TypeScript allows you to define multiple tags for more complex data structuring needs. Here's an example demonstrating the use of multiple tags within a single struct:

  import { Schema } from "@​effect/schema";
  
  const Product = Schema.TaggedStruct("Product", {
    category: Schema.tag("Electronics"),
    name: Schema.String,
    price: Schema.Number,
  });
  
  // `_tag` and `category` are optional
  const productInstance = Product.make({ name: "Smartphone", price: 999 });
  
  assert.deepStrictEqual(productInstance, {
    _tag: "Product",
    category: "Electronics",
    name: "Smartphone",
    price: 999,
  });

  This example showcases a product schema that not only categorizes each product under a general tag ("Product") but also specifies a category tag ("Electronics"), enhancing the clarity and specificity of the data model.

Effect-TS/effect (effect)

v3.2.8

Compare Source

Patch Changes

• #​2894 fb91f17 Thanks @​mikearnaldi! - ensure Equal considers Date by value

v3.2.7

Compare Source

Patch Changes

• #​2887 6801fca Thanks @​mikearnaldi! - Ensure provide of runtime is additive on context

v3.2.6

Compare Source

Patch Changes

• #​2879 cc8ac50 Thanks @​TylorS! - Support tuples in Types.DeepMutable

pnpm/pnpm (pnpm)

v9.1.4

Compare Source

v9.1.3

Compare Source

v9.1.2

Compare Source

Patch Changes

• Reduced memory usage during peer dependencies resolution #​8084.
• Details in the pnpm licenses output are not misplaced anymore #​8071.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

privatenumber/tsx (tsx)

v4.11.2

Compare Source

v4.11.1

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.