search

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 #391

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.37.0
@effect/platform 0.55.5 0.58.19
@effect/platform-node 0.51.5 0.53.18
@effect/printer 0.33.24 0.33.38
@effect/printer-ansi 0.33.24 0.33.38
@effect/schema 0.67.18 0.68.16
effect 3.2.8 3.4.6

Updates @effect/cli from 0.36.40 to 0.37.0

Release notes

Sourced from @​effect/cli's releases.

@​effect/cli@​0.37.0

Minor Changes

  • #3153 51bb7d5 Thanks @​IMax153! - Refactors the Prompt.custom constructor to make it easier to create custom Prompts.

    The Prompt.custom constructor allows for creation of a custom Prompt from the provided initial state and handlers.

    export const custom: <State, Output>(
  initialState: State | Effect<State, never, Prompt.Environment>,
  handlers: {
    readonly render: (
      state: State,
      action: Action<State, Output>,
    ) => Effect<string, never, Environment>;
    readonly process: (
      input: UserInput,
      state: State,
    ) => Effect<Action<State, Output>, never, Environment>;
    readonly clear: (
      state: State,
      action: Action<State, Output>,
    ) => Effect<string, never, Environment>;
  },
) => Prompt<Output> = InternalPrompt.custom;

    The initial state of a Prompt can either be a pure value or an Effect. This is particularly useful when the initial state of the Prompt must be computed by performing some effectful computation, such as reading data from the file system.

    A Prompt is essentially a render loop where user input triggers a new frame to be rendered to the Terminal. The handlers of a custom prompt are used to control what is rendered to the Terminal each frame. During each frame, the following occurs:

    1. The render handler is called with this frame's prompt state and prompt action and returns an ANSI escape string to be rendered to the Terminal
    2. The Terminal obtains input from the user
    3. The process handler is called with the input obtained from the user and this frame's prompt state and returns the next prompt action that should be performed
    4. The clear handler is called with this frame's prompt state and prompt action and returns an ANSI escape string used to clear the screen of the Terminal

... (truncated)

Changelog

Sourced from @​effect/cli's changelog.

0.37.0

Minor Changes

  • #3153 51bb7d5 Thanks @​IMax153! - Refactors the Prompt.custom constructor to make it easier to create custom Prompts.

    The Prompt.custom constructor allows for creation of a custom Prompt from the provided initial state and handlers.

    export const custom: <State, Output>(
  initialState: State | Effect<State, never, Prompt.Environment>,
  handlers: {
    readonly render: (
      state: State,
      action: Action<State, Output>,
    ) => Effect<string, never, Environment>;
    readonly process: (
      input: UserInput,
      state: State,
    ) => Effect<Action<State, Output>, never, Environment>;
    readonly clear: (
      state: State,
      action: Action<State, Output>,
    ) => Effect<string, never, Environment>;
  },
) => Prompt<Output> = InternalPrompt.custom;

    The initial state of a Prompt can either be a pure value or an Effect. This is particularly useful when the initial state of the Prompt must be computed by performing some effectful computation, such as reading data from the file system.

    A Prompt is essentially a render loop where user input triggers a new frame to be rendered to the Terminal. The handlers of a custom prompt are used to control what is rendered to the Terminal each frame. During each frame, the following occurs:

    1. The render handler is called with this frame's prompt state and prompt action and returns an ANSI escape string to be rendered to the Terminal
    2. The Terminal obtains input from the user
    3. The process handler is called with the input obtained from the user and this frame's prompt state and returns the next prompt action that should be performed
    4. The clear handler is called with this frame's prompt state and prompt action and returns an ANSI escape string used to clear the screen of the Terminal

... (truncated)

Commits


Updates @effect/platform from 0.55.5 to 0.58.19

Release notes

Sourced from @​effect/platform's releases.

@​effect/platform@​0.58.19

Patch Changes

@​effect/platform@​0.58.18

Patch Changes

@​effect/platform@​0.58.17

Patch Changes

Changelog

Sourced from @​effect/platform's changelog.

0.58.19

Patch Changes

0.58.18

Patch Changes

0.58.17

Patch Changes

0.58.16

Patch Changes

  • Updated dependencies [61e5964]:
    • @​effect/schema@​0.68.14

0.58.15

Patch Changes

0.58.14

Patch Changes

0.58.13

Patch Changes

... (truncated)

Commits


Updates @effect/platform-node from 0.51.5 to 0.53.18

Release notes

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

@​effect/platform-node@​0.53.18

Patch Changes

  • Updated dependencies []:
    • @​effect/platform@​0.58.19
    • @​effect/platform-node-shared@​0.8.18

@​effect/platform-node@​0.53.17

Patch Changes

  • Updated dependencies [7f8900a]:
    • @​effect/platform@​0.58.18
    • @​effect/platform-node-shared@​0.8.17

@​effect/platform-node@​0.53.16

Patch Changes

Changelog

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

0.53.18

Patch Changes

  • Updated dependencies []:
    • @​effect/platform@​0.58.19
    • @​effect/platform-node-shared@​0.8.18

0.53.17

Patch Changes

  • Updated dependencies [7f8900a]:
    • @​effect/platform@​0.58.18
    • @​effect/platform-node-shared@​0.8.17

0.53.16

Patch Changes

0.53.15

Patch Changes

  • Updated dependencies []:
    • @​effect/platform@​0.58.16
    • @​effect/platform-node-shared@​0.8.15

0.53.14

Patch Changes

  • Updated dependencies [baa90df]:
    • @​effect/platform@​0.58.15
    • @​effect/platform-node-shared@​0.8.14

0.53.13

Patch Changes

0.53.12

... (truncated)

Commits


Updates @effect/printer from 0.33.24 to 0.33.38

Release notes

Sourced from @​effect/printer's releases.

@​effect/printer-ansi@​0.33.38

Patch Changes

@​effect/printer@​0.33.38

Patch Changes

Changelog

Sourced from @​effect/printer's changelog.

0.33.38

Patch Changes

0.33.37

Patch Changes

  • Updated dependencies [a047af9]:
    • effect@3.4.5
    • @​effect/typeclass@​0.24.37

0.33.36

Patch Changes

0.33.35

Patch Changes

0.33.34

Patch Changes

  • Updated dependencies [3da1497]:
    • effect@3.4.2
    • @​effect/typeclass@​0.24.34

0.33.33

Patch Changes

  • Updated dependencies [66a1910]:
    • effect@3.4.1
    • @​effect/typeclass@​0.24.33

... (truncated)

Commits


Updates @effect/printer-ansi from 0.33.24 to 0.33.38

Release notes

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

@​effect/printer-ansi@​0.33.38

Patch Changes

Changelog

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

0.33.38

Patch Changes

0.33.37

Patch Changes

  • Updated dependencies [a047af9]:
    • effect@3.4.5
    • @​effect/printer@​0.33.37
    • @​effect/typeclass@​0.24.37

0.33.36

Patch Changes

0.33.35

Patch Changes

0.33.34

Patch Changes

  • Updated dependencies [3da1497]:
    • effect@3.4.2
    • @​effect/printer@​0.33.34
    • @​effect/typeclass@​0.24.34

0.33.33

Patch Changes

... (truncated)

Commits


Updates @effect/schema from 0.67.18 to 0.68.16

Release notes

Sourced from @​effect/schema's releases.

@​effect/schema@​0.68.16

Patch Changes

  • #3143 d006cec Thanks @​gcanti! - Enhance JSON Schema Support for Refinements in Record Parameters.

    Enhanced JSONSchema.make to properly support refinements as record parameters. Previously, using refinements with Schema.Record resulted in errors when generating JSON schemas.

    Before

    import { JSONSchema, Schema } from "@effect/schema";

    const schema = Schema.Record(
    
Schema.String.pipe(Schema.minLength(1)),
    
Schema.Number,
    
);
    

    console.log(JSONSchema.make(schema));
    
/*
    
throws
    
Error: Unsupported index signature parameter
    
schema (Refinement): a string at least 1 character(s) long
    
*/

    Now

    import { JSONSchema, Schema } from "@effect/schema";

    const schema = Schema.Record(
    
Schema.String.pipe(Schema.minLength(1)),
    
Schema.Number,
    
);
    

    console.log(JSONSchema.make(schema));
    
/*
    
Output:
    
{
    
'$schema': 'http://json-schema.org/draft-07/schema#',
    
type: 'object',
    
required: [],
    
properties: {},
    
patternProperties: { '': { type: 'number' } },
    
propertyNames: {
    
type: 'string',
    
description: 'a string at least 1 character(s) long',
    
minLength: 1
    
}
    
}

... (truncated)

Changelog

Sourced from @​effect/schema's changelog.

0.68.16

Patch Changes

  • #3143 d006cec Thanks @​gcanti! - Enhance JSON Schema Support for Refinements in Record Parameters.

    Enhanced JSONSchema.make to properly support refinements as record parameters. Previously, using refinements with Schema.Record resulted in errors when generating JSON schemas.

    Before

    import { JSONSchema, Schema } from "@effect/schema";

    const schema = Schema.Record(
    
Schema.String.pipe(Schema.minLength(1)),
    
Schema.Number,
    
);
    

    console.log(JSONSchema.make(schema));
    
/*
    
throws
    
Error: Unsupported index signature parameter
    
schema (Refinement): a string at least 1 character(s) long
    
*/

    Now

    import { JSONSchema, Schema } from "@effect/schema";

    const schema = Schema.Record(
    
Schema.String.pipe(Schema.minLength(1)),
    
Schema.Number,
    
);
    

    console.log(JSONSchema.make(schema));
    
/*
    
Output:
    
{
    
'$schema': 'http://json-schema.org/draft-07/schema#',
    
type: 'object',
    
required: [],
    
properties: {},
    
patternProperties: { '': { type: 'number' } },
    
propertyNames: {
    
type: 'string',
    
description: 'a string at least 1 character(s) long',
    
minLength: 1
    
}

... (truncated)

Commits
  • 48e614e Version Packages (#3140)
  • cb22726 add PersistedCache module to /experimental (#3149)
  • 2530780 Add an example of a transformation where we need to use `Schema.typeS… (#3145)
  • d006cec Enhance JSON Schema Support for Refinements in Record Parameters (#3143)
  • e911cfd Optimize JSON Schema output for homogeneous tuples (such as non empty… (#3139)
  • a4982f6 Version Packages (#3128)
  • 8513d7e README: Recommend using the strict: true option to get better error… (#3132)
  • 34faeb6 Add ReadonlyMapFromRecord and MapFromRecord, closes #3119 (#3130)
  • 07be551 Version Packages (#3126)
  • 61e5964 Add support for Union, Suspend, and Refinement as the second argument… (#3125)
  • Additional commits viewable in compare view


Updates effect from 3.2.8 to 3.4.6

Release notes

Sourced from effect's releases.

effect@3.4.6

Patch Changes

  • #3096 5c0ceb0 Thanks @​gcanti! - Micro: align with Effect module (renamings and new combinators).

    General naming convention rule: <reference module (start with lowercase)><api (start with Uppercase)>.

    • Failure -> MicroCause
      • Failure.Expected<E> -> MicroCause.Fail<E>
      • Failure.Unexpected -> MicroCause.Die
      • Failure.Aborted -> MicroCause.Interrupt
      • FailureExpected -> causeFail
      • FailureUnexpected -> causeDie
      • FailureAborted -> causeInterrupt
      • failureIsExpected -> causeIsFail
      • failureIsExpected -> causeIsFail
      • failureIsUnexpected -> causeIsDie
      • failureIsAborted -> causeIsInterrupt
      • failureSquash -> causeSquash
      • failureWithTrace -> causeWithTrace
    • Result -> MicroExit
      • ResultAborted -> exitInterrupt
      • ResultSuccess -> exitSucceed
      • ResultFail -> exitFail
      • ResultFailUnexpected -> exitDie
      • ResultFailWith -> exitFailCause
      • resultIsSuccess -> exitIsSuccess
      • resultIsFailure -> exitIsFailure
      • resultIsAborted -> exitIsInterrupt
      • resultIsFailureExpected -> exitIsFail
      • resultIsFailureUnexpected -> exitIsDie
      • resultVoid -> exitVoid
    • DelayFn -> MicroSchedule
      • delayExponential -> scheduleExponential
      • delaySpaced -> scheduleSpaced
      • delayWithMax -> scheduleWithMaxDelay
      • delayWithMaxElapsed -> scheduleWithMaxElapsed
      • delayWithRecurs -> scheduleRecurs and make it a constructor
      • add scheduleAddDelay combinator
      • add scheduleUnion combinator
      • add scheduleIntersect combinator
    • Handle
      • abort -> interrupt
      • unsafeAbort -> unsafeInterrupt
    • provideServiceMicro -> provideServiceEffect
    • fromResult -> fromExit
    • fromResultSync -> fromExitSync
    • failWith -> failCause
    • failWithSync -> failCauseSync
    • asResult -> exit

... (truncated)

Changelog

Sourced from effect's changelog.

3.4.6

Patch Changes

  • #3096 5c0ceb0 Thanks @​gcanti! - Micro: align with Effect module (renamings and new combinators).

    General naming convention rule: <reference module (start with lowercase)><api (start with Uppercase)>.

    • Failure -> MicroCause
      • Failure.Expected<E> -> MicroCause.Fail<E>
      • Failure.Unexpected -> MicroCause.Die
      • Failure.Aborted -> MicroCause.Interrupt
      • FailureExpected -> causeFail
      • FailureUnexpected -> causeDie
      • FailureAborted -> causeInterrupt
      • failureIsExpected -> causeIsFail
      • failureIsExpected -> causeIsFail
      • failureIsUnexpected -> causeIsDie
      • failureIsAborted -> causeIsInterrupt
      • failureSquash -> causeSquash
      • failureWithTrace -> causeWithTrace
    • Result -> MicroExit
      • ResultAborted -> exitInterrupt
      • ResultSuccess -> exitSucceed
      • ResultFail -> exitFail
      • ResultFailUnexpected -> exitDie
      • ResultFailWith -> exitFailCause
      • resultIsSuccess -> exitIsSuccess
      • resultIsFailure -> exitIsFailure
      • resultIsAborted -> exitIsInterrupt
      • resultIsFailureExpected -> exitIsFail
      • resultIsFailureUnexpected -> exitIsDie
      • resultVoid -> exitVoid
    • DelayFn -> MicroSchedule
      • delayExponential -> scheduleExponential
      • delaySpaced -> scheduleSpaced
      • delayWithMax -> scheduleWithMaxDelay
      • delayWithMaxElapsed -> scheduleWithMaxElapsed
      • delayWithRecurs -> scheduleRecurs and make it a constructor
      • add scheduleAddDelay combinator
      • add scheduleUnion combinator
      • add scheduleIntersect combinator
    • Handle
      • abort -> interrupt
      • unsafeAbort -> unsafeInterrupt
    • provideServiceMicro -> provideServiceEffect
    • fromResult -> fromExit
    • fromResultSync -> fromExitSync
    • failWith -> failCause
    • failWithSync -> failCauseSync

... (truncated)

Commits


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 4 months ago

Superseded by #393.