ccntrq / git-jira-branch

Manage branches for your Jira tickets
https://www.npmjs.com/package/git-jira-branch
MIT License
11 stars 2 forks source link

fix(deps): bump the production-dependencies group across 1 directory with 7 updates #367

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps the production-dependencies group with 7 updates in the / directory:

Package From To
@effect/cli 0.36.40 0.36.46
@effect/platform 0.55.5 0.57.2
@effect/platform-node 0.51.5 0.51.11
@effect/printer 0.33.24 0.33.29
@effect/printer-ansi 0.33.24 0.33.29
@effect/schema 0.67.18 0.67.24
effect 3.2.8 3.3.3

Updates @effect/cli from 0.36.40 to 0.36.46

Release notes

Sourced from @​effect/cli's releases.

@​effect/cli@​0.36.46

Patch Changes

@​effect/cli@​0.36.45

Patch Changes

@​effect/cli@​0.36.44

Patch Changes

Changelog

Sourced from @​effect/cli's changelog.

0.36.46

Patch Changes

0.36.45

Patch Changes

0.36.44

Patch Changes

0.36.43

Patch Changes

0.36.42

Patch Changes

... (truncated)

Commits


Updates @effect/platform from 0.55.5 to 0.57.2

Release notes

Sourced from @​effect/platform's releases.

@​effect/platform@​0.57.2

Patch Changes

@​effect/platform@​0.57.1

Patch Changes

@​effect/platform@​0.57.0

Minor Changes

Patch Changes

Changelog

Sourced from @​effect/platform's changelog.

0.57.2

Patch Changes

0.57.1

Patch Changes

0.57.0

Minor Changes

Patch Changes

0.56.0

Minor Changes

Patch Changes

0.55.7

Patch Changes

... (truncated)

Commits


Updates @effect/platform-node from 0.51.5 to 0.51.11

Release notes

Sourced from @​effect/platform-node's releases.

@​effect/platform-node@​0.51.11

Patch Changes

  • Updated dependencies [06ede85, 7204ca5]:
    • effect@3.3.3
    • @​effect/platform@​0.57.2
    • @​effect/platform-node-shared@​0.6.11

@​effect/platform-node@​0.51.10

Patch Changes

@​effect/platform-node@​0.51.9

Patch Changes

Changelog

Sourced from @​effect/platform-node's changelog.

0.51.11

Patch Changes

  • Updated dependencies [06ede85, 7204ca5]:
    • effect@3.3.3
    • @​effect/platform@​0.57.2
    • @​effect/platform-node-shared@​0.6.11

0.51.10

Patch Changes

0.51.9

Patch Changes

0.51.8

Patch Changes

0.51.7

Patch Changes

  • Updated dependencies [a67d602]:
    • @​effect/platform@​0.55.7
    • @​effect/platform-node-shared@​0.6.7

0.51.6

Patch Changes

... (truncated)

Commits


Updates @effect/printer from 0.33.24 to 0.33.29

Release notes

Sourced from @​effect/printer's releases.

@​effect/printer@​0.33.29

Patch Changes

@​effect/printer-ansi@​0.33.29

Patch Changes

@​effect/printer-ansi@​0.33.28

Patch Changes

@​effect/printer@​0.33.28

Patch Changes

@​effect/printer-ansi@​0.33.27

Patch Changes

@​effect/printer@​0.33.27

Patch Changes

Changelog

Sourced from @​effect/printer's changelog.

0.33.29

Patch Changes

0.33.28

Patch Changes

0.33.27

Patch Changes

0.33.26

Patch Changes

0.33.25

Patch Changes

Commits


Updates @effect/printer-ansi from 0.33.24 to 0.33.29

Release notes

Sourced from @​effect/printer-ansi's releases.

@​effect/printer-ansi@​0.33.29

Patch Changes

@​effect/printer-ansi@​0.33.28

Patch Changes

@​effect/printer-ansi@​0.33.27

Patch Changes

Changelog

Sourced from @​effect/printer-ansi's changelog.

0.33.29

Patch Changes

0.33.28

Patch Changes

0.33.27

Patch Changes

0.33.26

Patch Changes

0.33.25

Patch Changes

Commits


Updates @effect/schema from 0.67.18 to 0.67.24

Release notes

Sourced from @​effect/schema's releases.

@​effect/schema@​0.67.24

Patch Changes

  • #2997 3b15e1b Thanks @​gcanti! - Improve error handling (type-level) for improper usage of optional, closes #2995

    This commit addresses concerns raised by users about the confusing behavior when 'optional' is misused in a schema definition. Previously, users experienced unexpected results, such as a schema returning 'Schema.All' when 'optional' was used incorrectly, without clear guidance on the correct usage or error messages.

    Changes:

    • Enhanced the 'optional' method to return a descriptive type-level error when used incorrectly, helping users identify and correct their schema definitions.
    • Updated the Schema.optional() implementation to check its context within a pipeline and ensure it is being used correctly.
    • Added unit tests to verify that the new error handling works as expected and to ensure that correct usage does not affect existing functionality.
  • #2994 3a750b2 Thanks @​gcanti! - Expose exact option for strict decoding on missing properties, closes #2993

    This commit addresses an issue where users encountered unexpected decoding behaviors, specifically regarding how undefined values and missing properties are handled. The default behavior of the @effect/schema library treats missing properties as undefined during decoding, which can lead to confusion when stricter validation is expected.

    Changes:

    • Exposed an internal configuration option exțact (default: false), which when set to true, enforces strict decoding that will error on missing properties instead of treating them as undefined.
    • Updated documentation to clearly outline the default and strict decoding behaviors, providing users with guidance on how to enable strict validation.
  • Updated dependencies [06ede85, 7204ca5]:

    • effect@3.3.3

@​effect/schema@​0.67.23

Patch Changes

@​effect/schema@​0.67.22

Patch Changes

@​effect/schema@​0.67.21

Patch Changes

... (truncated)

Changelog

Sourced from @​effect/schema's changelog.

0.67.24

Patch Changes

  • #2997 3b15e1b Thanks @​gcanti! - Improve error handling (type-level) for improper usage of optional, closes #2995

    This commit addresses concerns raised by users about the confusing behavior when 'optional' is misused in a schema definition. Previously, users experienced unexpected results, such as a schema returning 'Schema.All' when 'optional' was used incorrectly, without clear guidance on the correct usage or error messages.

    Changes:

    • Enhanced the 'optional' method to return a descriptive type-level error when used incorrectly, helping users identify and correct their schema definitions.
    • Updated the Schema.optional() implementation to check its context within a pipeline and ensure it is being used correctly.
    • Added unit tests to verify that the new error handling works as expected and to ensure that correct usage does not affect existing functionality.
  • #2994 3a750b2 Thanks @​gcanti! - Expose exact option for strict decoding on missing properties, closes #2993

    This commit addresses an issue where users encountered unexpected decoding behaviors, specifically regarding how undefined values and missing properties are handled. The default behavior of the @effect/schema library treats missing properties as undefined during decoding, which can lead to confusion when stricter validation is expected.

    Changes:

    • Exposed an internal configuration option exțact (default: false), which when set to true, enforces strict decoding that will error on missing properties instead of treating them as undefined.
    • Updated documentation to clearly outline the default and strict decoding behaviors, providing users with guidance on how to enable strict validation.
  • Updated dependencies [06ede85, 7204ca5]:

    • effect@3.3.3

0.67.23

Patch Changes

  • #2991... _Description has been truncated_

dependabot[bot] commented 4 months ago

Superseded by #369.