Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

⬆️ Update dependency @effect/schema to v0.75.5 #56

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 5, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@effect/schema (source) 0.60.4 -> 0.75.5 age adoption passing confidence

Release Notes

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

v0.75.5

Compare Source

Patch Changes
  • #​3792 382556f Thanks @​gcanti! - resolve parse error when using pick with union of class schemas, closes #​3751

  • #​3790 97cb014 Thanks @​gcanti! - Equivalence: Fixed a bug related to discriminated tuples.

    Example:

    The following equivalence check was incorrectly returning false:

    import * as E from "@​effect/schema/Equivalence"
    import * as S from "@​effect/schema/Schema"
    
    // Union of discriminated tuples
    const schema = S.Union(
      S.Tuple(S.Literal("a"), S.String),
      S.Tuple(S.Literal("b"), S.Number)
    )
    
    const equivalence = E.make(schema)
    
    console.log(equivalence(["a", "x"], ["a", "x"]))
    // false

v0.75.4

Compare Source

Patch Changes

v0.75.3

Compare Source

Patch Changes
  • #​3761 360ec14 Thanks @​gcanti! - Allow Schema.Either to support Schema.Never without type errors, closes #​3755.

    • Updated the type parameters of format to extend Schema.All instead of Schema<A, I, R>.
    • Updated the type parameters of Schema.EitherFromSelf to extend Schema.All instead of Schema.Any.
    • Updated the type parameters of Schema.Either to extend Schema.All instead of Schema.Any.
    • Updated the type parameters of Schema.EitherFromUnion to extend Schema.All instead of Schema.Any.

v0.75.2

Compare Source

Patch Changes
  • #​3753 f02b354 Thanks @​gcanti! - Enhanced Error Reporting for Discriminated Union Tuple Schemas, closes #​3752

    Previously, irrelevant error messages were generated for each member of the union. Now, when a discriminator is present in the input, only the relevant member will trigger an error.

    Before

    import * as Schema from "@&#8203;effect/schema/Schema"
    
    const schema = Schema.Union(
      Schema.Tuple(Schema.Literal("a"), Schema.String),
      Schema.Tuple(Schema.Literal("b"), Schema.Number)
    ).annotations({ identifier: "MyUnion" })
    
    console.log(Schema.decodeUnknownSync(schema)(["a", 0]))
    /*
    throws:
    ParseError: MyUnion
    ├─ readonly ["a", string]
    │  └─ [1]
    │     └─ Expected string, actual 0
    └─ readonly ["b", number]
       └─ [0]
          └─ Expected "b", actual "a"
    */

    After

    import * as Schema from "@&#8203;effect/schema/Schema"
    
    const schema = Schema.Union(
      Schema.Tuple(Schema.Literal("a"), Schema.String),
      Schema.Tuple(Schema.Literal("b"), Schema.Number)
    ).annotations({ identifier: "MyUnion" })
    
    console.log(Schema.decodeUnknownSync(schema)(["a", 0]))
    /*
    throws:
    ParseError: MyUnion
    └─ readonly ["a", string]
       └─ [1]
          └─ Expected string, actual 0
    */

v0.75.1

Compare Source

Patch Changes

v0.75.0

Compare Source

Minor Changes
Patch Changes

v0.74.2

Compare Source

Patch Changes

v0.74.1

Compare Source

Patch Changes
  • #​3669 734eae6 Thanks @​gcanti! - Add description annotation to the encoded part of NumberFromString.

    Before

    import { JSONSchema, Schema } from "@&#8203;effect/schema"
    
    const schema = Schema.NumberFromString
    
    console.log(JSON.stringify(JSONSchema.make(schema), null, 2))
    /*
    {
      "$schema": "http://json-schema.org/draft-07/schema#",
      "type": "string"
    }
    */

    After

    import { JSONSchema, Schema } from "@&#8203;effect/schema"
    
    const schema = Schema.NumberFromString
    
    console.log(JSON.stringify(JSONSchema.make(schema), null, 2))
    /*
    {
      "$schema": "http://json-schema.org/draft-07/schema#",
      "type": "string",
      "description": "a string that will be parsed into a number"
    }
    */
  • #​3667 fd83d0e Thanks @​gcanti! - Remove default json schema annotations from string, number and boolean.

    Before

    import { JSONSchema, Schema } from "@&#8203;effect/schema"
    
    const schema = Schema.String.annotations({ examples: ["a", "b"] })
    
    console.log(JSON.stringify(JSONSchema.make(schema), null, 2))
    /*
    {
      "$schema": "http://json-schema.org/draft-07/schema#",
      "type": "string",
      "description": "a string",
      "title": "string",
      "examples": [
        "a",
        "b"
      ]
    }
    */

    After

    import { JSONSchema, Schema } from "@&#8203;effect/schema"
    
    const schema = Schema.String.annotations({ examples: ["a", "b"] })
    
    console.log(JSON.stringify(JSONSchema.make(schema), null, 2))
    /*
    {
      "$schema": "http://json-schema.org/draft-07/schema#",
      "type": "string",
      "examples": [
        "a",
        "b"
      ]
    }
    */
  • #​3673 ad7e1de Thanks @​gcanti! - Add more description annotations.

  • #​3672 090e41c Thanks @​gcanti! - JSON Schema: handle refinements where the 'from' part includes a transformation, closes #​3662

    Before

    import { JSONSchema, Schema } from "@&#8203;effect/schema"
    
    const schema = Schema.Date
    
    console.log(JSON.stringify(JSONSchema.make(schema), null, 2))
    /*
    throws
    Error: Missing annotation
    details: Generating a JSON Schema for this schema requires a "jsonSchema" annotation
    schema (Refinement): Date
    */

    After

    import { JSONSchema, Schema } from "@&#8203;effect/schema"
    
    const schema = Schema.Date
    
    console.log(JSON.stringify(JSONSchema.make(schema), null, 2))
    /*
    {
      "$schema": "http://json-schema.org/draft-07/schema#",
      "type": "string",
      "description": "a string that will be parsed into a Date"
    }
    */
  • #​3672 090e41c Thanks @​gcanti! - Add description annotation to the encoded part of DateFromString.

    Before

    import { JSONSchema, Schema } from "@&#8203;effect/schema"
    
    const schema = Schema.DateFromString
    
    console.log(JSON.stringify(JSONSchema.make(schema), null, 2))
    /*
    {
      "$schema": "http://json-schema.org/draft-07/schema#",
      "type": "string"
    }
    */

    After

    import { JSONSchema, Schema } from "@&#8203;effect/schema"
    
    const schema = Schema.DateFromString
    
    console.log(JSON.stringify(JSONSchema.make(schema), null, 2))
    /*
    {
      "$schema": "http://json-schema.org/draft-07/schema#",
      "type": "string",
      "description": "a string that will be parsed into a Date"
    }
    */
  • Updated dependencies [4509656]:

v0.74.0

Compare Source

Minor Changes

v0.73.4

Compare Source

Patch Changes

v0.73.3

Compare Source

Patch Changes
  • #​3635 e6440a7 Thanks @​gcanti! - Stable filters such as minItems, maxItems, and itemsCount now generate multiple errors when the 'errors' option is set to 'all', closes #​3633

    Example:

    import { ArrayFormatter, Schema } from "@&#8203;effect/schema"
    
    const schema = Schema.Struct({
      tags: Schema.Array(Schema.String.pipe(Schema.minLength(2))).pipe(
        Schema.minItems(3)
      )
    })
    
    const invalidData = { tags: ["AB", "B"] }
    
    const either = Schema.decodeUnknownEither(schema, { errors: "all" })(
      invalidData
    )
    if (either._tag === "Left") {
      console.log(ArrayFormatter.formatErrorSync(either.left))
      /*
      Output:
      [
        {
          _tag: 'Type',
          path: [ 'tags', 1 ],
          message: 'Expected a string at least 2 character(s) long, actual "B"'
        },
        {
          _tag: 'Type',
          path: [ 'tags' ],
          message: 'Expected an array of at least 3 items, actual ["AB","B"]'
        }
      ]
      */
    }

    Previously, only the issue related to the [ 'tags', 1 ] path was reported.

v0.73.2

Compare Source

Patch Changes

v0.73.1

Compare Source

Patch Changes

v0.73.0

Compare Source

Minor Changes
  • #​3589 7fdf9d9 Thanks @​gcanti! - Updates the constraints for members within a union from the more restrictive Schema.Any to the more inclusive Schema.All, closes #​3587.

    Affected APIs include:

    • Schema.Union
    • Schema.UndefinedOr
    • Schema.NullOr
    • Schema.NullishOr
    • Schema.optional
    • AST.Union.make now retains duplicate members and no longer eliminates the neverKeyword.
Patch Changes

v0.72.4

Compare Source

Patch Changes

v0.72.3

Compare Source

Patch Changes

v0.72.2

Compare Source

Patch Changes

v0.72.1

Compare Source

Patch Changes

v0.72.0

Compare Source

Patch Changes

v0.71.4

Compare Source

Patch Changes

v0.71.3

Compare Source

Patch Changes

v0.71.2

Compare Source

Patch Changes

v0.71.1

Compare Source

Patch Changes

v0.71.0

Compare Source

Minor Changes
  • #​3433 c1987e2 Thanks @​gcanti! - Make json schema output more compatible with Open AI structured output, closes #​3432.

    JSONSchema

    • remove oneOf in favour of anyOf (e.g. in JsonSchema7object, JsonSchema7empty, JsonSchema7Enums)
    • remove const in favour of enum (e.g. in JsonSchema7Enums)
    • remove JsonSchema7Const type
    • remove JsonSchema7OneOf type

    AST

    • remove identifier annotation from Schema.Null
    • remove identifier annotation from Schema.Object
Patch Changes
  • #​3448 1ceed14 Thanks @​tim-smart! - add Schema.ArrayEnsure & Schema.NonEmptyArrayEnsure

    These schemas can be used to ensure that a value is an array, from a value that may be an array or a single value.

    import { Schema } from "@&#8203;effect/schema";
    
    const schema = Schema.ArrayEnsure(Schema.String);
    
    Schema.decodeUnknownSync(schema)("hello");
    // => ["hello"]
    
    Schema.decodeUnknownSync(schema)(["a", "b", "c"]);
    // => ["a", "b", "c"]
  • #​3450 0e42a8f Thanks @​tim-smart! - update dependencies

  • Updated dependencies [8295281, c940df6, 00b6c6d, f8d95a6]:

v0.70.4

Compare Source

Patch Changes

v0.70.3

Compare Source

Patch Changes
  • #​3430 99ad841 Thanks @​gcanti! - Fix return types for attachPropertySignature function.

    This commit addresses an inconsistency in the return types between the curried and non-curried versions of the attachPropertySignature function. Previously, the curried version returned a Schema, while the non-curried version returned a SchemaClass.

  • Updated dependencies [fd4b2f6]:

v0.70.2

Compare Source

Patch Changes

v0.70.1

Compare Source

Patch Changes
  • #​3347 3dce357 Thanks @​gcanti! - Enhanced Parsing with TemplateLiteralParser, closes #​3307

    In this update we've introduced a sophisticated API for more refined string parsing: TemplateLiteralParser. This enhancement stems from recognizing limitations in the Schema.TemplateLiteral and Schema.pattern functionalities, which effectively validate string formats without extracting structured data.

    Overview of Existing Limitations

    The Schema.TemplateLiteral function, while useful as a simple validator, only verifies that an input conforms to a specific string pattern by converting template literal definitions into regular expressions. Similarly, Schema.pattern employs regular expressions directly for the same purpose. Post-validation, both methods require additional manual parsing to convert the validated string into a usable data format.

    Introducing TemplateLiteralParser

    To address these limitations and eliminate the need for manual post-validation parsing, the new TemplateLiteralParser API has been developed. It not only validates the input format but also automatically parses it into a more structured and type-safe output, specifically into a tuple format.

    This new approach enhances developer productivity by reducing boilerplate code and simplifying the process of working with complex string inputs.

    Example (string based schemas)

    import { Schema } from "@&#8203;effect/schema";
    
    // const schema: Schema.Schema<readonly [number, "a", string], `${string}a${string}`, never>
    const schema = Schema.TemplateLiteralParser(
      Schema.NumberFromString,
      "a",
      Schema.NonEmptyString,
    );
    
    console.log(Schema.decodeEither(schema)("100ab"));
    // { _id: 'Either', _tag: 'Right', right: [ 100, 'a', 'b' ] }
    
    console.log(Schema.encode(schema)([100, "a", "b"]));
    // { _id: 'Either', _tag: 'Right', right: '100ab' }

    Example (number based schemas)

    import { Schema } from "@&#8203;effect/schema";
    
    // const schema: Schema.Schema<readonly [number, "a"], `${number}a`, never>
    const schema = Schema.TemplateLiteralParser(Schema.Int, "a");
    
    console.log(Schema.decodeEither(schema)("1a"));
    // { _id: 'Either', _tag: 'Right', right: [ 1, 'a' ] }
    
    console.log(Schema.encode(schema)([1, "a"]));
    // { _id: 'Either', _tag: 'Right', right: '1a' }
  • #​3346 657fc48 Thanks @​gcanti! - Implement DecodingFallbackAnnotation to manage decoding errors.

    export type DecodingFallbackAnnotation<A> = (
      issue: ParseIssue,
    ) => Effect<A, ParseIssue>;

    This update introduces a decodingFallback annotation, enabling custom handling of decoding failures in schemas. This feature allows developers to specify fallback behaviors when decoding operations encounter issues.

    Example

    import { Schema } from "@&#8203;effect/schema";
    import { Effect, Either } from "effect";
    
    // Basic Fallback
    
    const schema = Schema.String.annotations({
      decodingFallback: () => Either.right("<fallback>"),
    });
    
    console.log(Schema.decodeUnknownSync(schema)("valid input")); // Output: valid input
    console.log(Schema.decodeUnknownSync(schema)(null)); // Output: <fallback value>
    
    // Advanced Fallback with Logging
    
    const schemaWithLog = Schema.String.annotations({
      decodingFallback: (issue) =>
        Effect.gen(function* () {
          yield* Effect.log(issue._tag);
          yield* Effect.sleep(10);
          return yield* Effect.succeed("<fallback2>");
        }),
    });
    
    Effect.runPromise(Schema.decodeUnknown(schemaWithLog)(null)).then(
      console.log,
    );
    /*
    Output:
    timestamp=2024-07-25T13:22:37.706Z level=INFO fiber=#&#8203;0 message=Type
    <fallback2>
    */

v0.70.0

Compare Source

Patch Changes

v0.69.3

Compare Source

Patch Changes
  • #​3359 7c0da50 Thanks @​gcanti! - Add Context field to Schema interface, closes #​3356

  • #​3363 2fc0ff4 Thanks @​gcanti! - export isPropertySignature guard

  • #​3357 f262665 Thanks @​gcanti! - Improve annotation retrieval from Class APIs, closes #​3348.

    Previously, accessing annotations such as identifier and title required explicit casting of the ast field to AST.Transformation.
    This update refines the type definitions to reflect that ast is always an AST.Transformation, eliminating the need for casting and simplifying client code.

    import { AST, Schema } from "@&#8203;effect/schema";
    
    class Person extends Schema.Class<Person>("Person")(
      {
        name: Schema.String,
        age: Schema.Number,
      },
      { description: "my description" },
    ) {}
    
    console.log(AST.getDescriptionAnnotation(Person.ast.to));
    // { _id: 'Option', _tag: 'Some', value: 'my description' }
  • #​3343 9bbe7a6 Thanks @​gcanti! - - add NonEmptyTrimmedString

    Example

    import { Schema } from "@&#8203;effect/schema";
    
    console.log(Schema.decodeOption(Schema.NonEmptyTrimmedString)("")); // Option.none()
    console.log(Schema.decodeOption(Schema.NonEmptyTrimmedString)(" a ")); // Option.none()
    console.log(Schema.decodeOption(Schema.NonEmptyTrimmedString)("a")); // Option.some("a")
    • add OptionFromNonEmptyTrimmedString, closes #​3335

      Example

      import { Schema } from "@&#8203;effect/schema";
      
      console.log(Schema.decodeSync(Schema.OptionFromNonEmptyTrimmedString)("")); // Option.none()
      console.log(
        Schema.decodeSync(Schema.OptionFromNonEmptyTrimmedString)(" a "),
      ); // Option.some("a")
      console.log(Schema.decodeSync(Schema.OptionFromNonEmptyTrimmedString)("a")); // Option.some("a")
  • Updated dependencies [6359644, 7f41e42, f566fd1]:

v0.69.2

Compare Source

Patch Changes

v0.69.1

Compare Source

Patch Changes

v0.69.0

Compare Source

Minor Changes
  • #​3227 20807a4 Thanks @​gcanti! - ## Codemod

    For some of the breking changes, a code-mod has been released to make migration as easy as possible.

    You can run it by executing:

    npx @&#8203;effect/codemod schema-0.69 src/**/*

    It might not be perfect - if you encounter issues, let us know! Also make sure you commit any changes before running it, in case you need to revert anything.

v0.68.27

Compare Source

Patch Changes

v0.68.26

Compare Source

Patch Changes
  • #​3287 f0285d3 Thanks @​gcanti! - JSON Schema: change default behavior for property signatures containing undefined

    Changed the default behavior when encountering a required property signature whose type contains undefined. Instead of raising an exception, undefined is now pruned and the field is set as optional.

    Before

    import { JSONSchema, Schema } from "@&#8203;effect/schema";
    
    const schema = Schema.Struct({
      a: Schema.NullishOr(Schema.Number),
    });
    
    const jsonSchema = JSONSchema.make(schema);
    console.log(JSON.stringify(jsonSchema, null, 2));
    /*
    throws
    Error: Missing annotation
    at path: ["a"]
    details: Generating a JSON Schema for this schema requires a "jsonSchema" annotation
    schema (UndefinedKeyword): undefined
    */

    Now

    import { JSONSchema, Schema } from "@&#8203;effect/schema";
    
    const schema = Schema.Struct({
      a: Schema.NullishOr(Schema.Number),
    });
    
    const jsonSchema = JSONSchema.make(schema);
    console.log(JSON.stringify(jsonSchema, null, 2));
    /*
    {
      "$schema": "http://json-schema.org/draft-07/schema#",
      "type": "object",
      "required": [], // <=== empty
      "properties": {
        "a": {
          "anyOf": [
            {
              "type": "number"
            },
            {
              "$ref": "#/$defs/null"
            }
          ]
        }
      },
      "additionalProperties": false,
      "$defs": {
        "null": {
          "const": null
        }
      }
    }
    */
  • #​3291 8ec4955 Thanks @​gcanti! - remove type-level error message from optional signature, closes #​3290

    This fix eliminates the type-level error message from the optional function signature, which was causing issues in generic contexts.

  • #​3284 3ac2d76 Thanks @​gcanti! - Fix: Correct Handling of JSON Schema Annotations in Refinements

    Fixes an issue where the JSON schema annotation set by a refinement after a transformation was mistakenly interpreted as an override annotation. This caused the output to be incorrect, as the annotations were not applied as intended.

    Before

    import { JSONSchema, Schema } from "@&#8203;effect/schema";
    
    const schema = Schema.Trim.pipe(Schema.nonEmpty());
    
    const jsonSchema = JSONSchema.make(schema);
    console.log(JSON.stringify(jsonSchema, null, 2));
    /*
    {
      "$schema": "http://json-schema.org/draft-07/schema#",
      "minLength": 1
    }
    */

    Now

    import { JSONSchema, Schema } from "@&#8203;effect/schema";
    
    const schema = Schema.Trim.pipe(Schema.nonEmpty());
    
    const jsonSchema = JSONSchema.make(schema);
    console.log(JSON.stringify(jsonSchema, null, 2));
    /*
    {
      "$schema": "http://json-schema.org/draft-07/schema#",
      "type": "string"
    }
    */
  • Updated dependencies [cc327a1, 4bfe4fb, 2b14d18]:

v0.68.25

Compare Source

Patch Changes

v0.68.24

Compare Source

Patch Changes

v0.68.23

Compare Source

Patch Changes

v0.68.22

Compare Source

Patch Changes

v0.68.21

Compare Source

Patch Changes

v0.68.20

Compare Source

Patch Changes

v0.68.19

Compare Source

Patch Changes

v0.68.18

Compare Source

Patch Changes
  • #​3192 5d5cc6c Thanks @​KhraksMamtsov! - Support Capitalize Uncapitalize filters and schemas

  • #​3148 359ff8a Thanks @​gcanti! - add Serializable.Serializable.Type and Serializable.Serializable.Encoded

  • #​3198 f7534b9 Thanks @​gcanti! - Add toString to AST.PropertySignature and AST.IndexSignature and fix type display for IndexSignature.

    Before the Change

    Previously, when a type mismatch occurred in Schema.decodeUnknownSync, the error message displayed for IndexSignature was not accurately representing the type used. For example:

    import { Schema } from "@&#8203;effect/schema";
    
    const schema = Schema.Record(Schema.Char, Schema.String);
    
    Schema.decodeUnknownSync(schema)({ a: 1 });
    /*
    throws
    ParseError: { readonly [x: string]: string }
    └─ ["a"]
       └─ Expected string, actual 1
    */

    This output incorrectly indicated [x: string] when the actual index type was Char.

    After the Change

    The toString implementation now correctly reflects the type used in IndexSignature, providing more accurate and informative error messages:

    import { Schema } from "@&#8203;effect/schema";
    
    const schema = Schema.Record(Schema.Char, Schema.String);
    
    Schema.decodeUnknownSync(schema)({ a: 1 });
    /*
    throws
    ParseError: { readonly [x: Char]: string }
    └─ ["a"]
       └─ Expected string, actual 1
    */

    The updated output now correctly displays { readonly [x: Char]: string }, aligning the error messages with the actual data types used in the schema.

  • Updated dependencies [a435e0f, b5554db, a9c4fb3]:

v0.68.17

Compare Source

Patch Changes
  • #​3166 15967cf Thanks @​gcanti! - Add filterEffect API, closes #​3165

    The filterEffect function enhances the filter functionality by allowing the integration of effects, thus enabling asynchronous or dynamic validation scenarios. This is particularly useful when validations need to perform operations that require side effects, such as network requests or database queries.

    Example: Validating Usernames Asynchronously

    import { Schema } from "@&#8203;effect/schema";
    import

Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added renovate upgrade Any kind of dependency updates labels Feb 5, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Feb 5, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch 2 times, most recently from 7f3e2a6 to fcafb0a Compare February 6, 2024 03:04
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from fcafb0a to 63daa91 Compare February 6, 2024 07:25
renovate-approve[bot]
renovate-approve bot previously approved these changes Feb 6, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch 9 times, most recently from 00e63db to 177abaa Compare February 6, 2024 19:16
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from 177abaa to 8e805c3 Compare February 7, 2024 22:43
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.61.5 ⬆️ Update dependency @effect/schema to v0.61.6 Feb 7, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Feb 7, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from 8e805c3 to 888ee5f Compare February 8, 2024 00:05
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.61.6 ⬆️ Update dependency @effect/schema to v0.61.7 Feb 8, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Feb 8, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Feb 8, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from c9dbf10 to dbbb409 Compare September 20, 2024 03:23
renovate-approve[bot]
renovate-approve bot previously approved these changes Sep 20, 2024
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.73.3 ⬆️ Update dependency @effect/schema to v0.73.4 Sep 20, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from dbbb409 to 3216f6f Compare September 23, 2024 00:50
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.73.4 ⬆️ Update dependency @effect/schema to v0.74.0 Sep 23, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Sep 23, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch 2 times, most recently from 55d97b7 to c24c2bb Compare September 24, 2024 02:31
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from c24c2bb to ce8ed4c Compare September 25, 2024 04:51
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.74.0 ⬆️ Update dependency @effect/schema to v0.74.1 Sep 25, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch 3 times, most recently from 6e8b52e to 01edafa Compare September 30, 2024 03:58
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from 01edafa to c547826 Compare October 6, 2024 22:51
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.74.1 ⬆️ Update dependency @effect/schema to v0.74.2 Oct 6, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from c547826 to b4af5ae Compare October 7, 2024 01:45
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.74.2 ⬆️ Update dependency @effect/schema to v0.75.0 Oct 7, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from b4af5ae to 92fb4f1 Compare October 7, 2024 22:15
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.75.0 ⬆️ Update dependency @effect/schema to v0.75.1 Oct 7, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from 92fb4f1 to 5aac98b Compare October 9, 2024 00:53
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.75.1 ⬆️ Update dependency @effect/schema to v0.75.2 Oct 9, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from 5aac98b to 741ae52 Compare October 11, 2024 03:18
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.75.2 ⬆️ Update dependency @effect/schema to v0.75.3 Oct 11, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from 741ae52 to 98d7885 Compare October 13, 2024 21:34
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.75.3 ⬆️ Update dependency @effect/schema to v0.75.4 Oct 13, 2024
@renovate renovate bot force-pushed the renovate/effect-schema-0.x branch from 98d7885 to 4da901d Compare October 16, 2024 15:20
@renovate renovate bot changed the title ⬆️ Update dependency @effect/schema to v0.75.4 ⬆️ Update dependency @effect/schema to v0.75.5 Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
renovate upgrade Any kind of dependency updates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants