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

Closed dependabot[bot] closed 5 months ago

dependabot[bot] commented 5 months ago

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

Package From To
@effect/cli 0.36.40 0.36.43
@effect/platform 0.55.5 0.56.0
@effect/platform-node 0.51.5 0.51.8
@effect/printer 0.33.24 0.33.26
@effect/printer-ansi 0.33.24 0.33.26
@effect/schema 0.67.18 0.67.21
effect 3.2.8 3.3.0

Updates @effect/cli from 0.36.40 to 0.36.43

Release notes

Sourced from @​effect/cli's releases.

@​effect/cli@​0.36.43

Patch Changes

@​effect/cli@​0.36.42

Patch Changes

@​effect/cli@​0.36.41

Patch Changes

Changelog

Sourced from @​effect/cli's changelog.

0.36.43

Patch Changes

0.36.42

Patch Changes

0.36.41

Patch Changes

Commits


Updates @effect/platform from 0.55.5 to 0.56.0

Release notes

Sourced from @​effect/platform's releases.

@​effect/platform@​0.56.0

Minor Changes

Patch Changes

@​effect/platform@​0.55.7

Patch Changes

@​effect/platform@​0.55.6

Patch Changes

  • #2903 799aa20 Thanks @​rocwang! - # Make baseUrl() more defensive in @​effect/platform

    Sometimes, third party code may patch a missing global location to accommodate for non-browser JavaScript runtimes, e.g. Cloudflare Workers, Deno. Such patch might not yield a fully valid location. This could break baseUrl(), which is called by makeUrl().

    For example, the following code would log Invalid URL: '/api/v1/users' with base 'NaN'.

    import { makeUrl } from "@effect/platform/Http/UrlParams";

    globalThis.location = { href: "" };
    

    const url = makeUrl("/api/v1/users", []);
    

    // This would log "Invalid URL: '/api/v1/users' with base 'NaN'",
// because location.origin + location.pathname return NaN in baseUrl()
console.log(url.left.message);

    Arguably, this is not an issue of Effect per se, but it's better to be defensive and handle such cases gracefully. So this change does that by checking if location.orign and location.pathname are available before accessing them.

  • Updated dependencies [8c5d280, 6ba6d26, cd7496b, 3f28bf2, 5817820, 349a036]:

... (truncated)

Changelog

Sourced from @​effect/platform's changelog.

0.56.0

Minor Changes

Patch Changes

0.55.7

Patch Changes

0.55.6

Patch Changes

  • #2903 799aa20 Thanks @​rocwang! - # Make baseUrl() more defensive in @​effect/platform

    Sometimes, third party code may patch a missing global location to accommodate for non-browser JavaScript runtimes, e.g. Cloudflare Workers, Deno. Such patch might not yield a fully valid location. This could break baseUrl(), which is called by makeUrl().

    For example, the following code would log Invalid URL: '/api/v1/users' with base 'NaN'.

    import { makeUrl } from "@effect/platform/Http/UrlParams";

    globalThis.location = { href: "" };
    

    const url = makeUrl("/api/v1/users", []);
    

    // This would log "Invalid URL: '/api/v1/users' with base 'NaN'",
// because location.origin + location.pathname return NaN in baseUrl()
console.log(url.left.message);

    Arguably, this is not an issue of Effect per se, but it's better to be defensive and handle such cases gracefully.

... (truncated)

Commits


Updates @effect/platform-node from 0.51.5 to 0.51.8

Release notes

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

@​effect/platform-node@​0.51.8

Patch Changes

@​effect/platform-node@​0.51.7

Patch Changes

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

@​effect/platform-node@​0.51.6

Patch Changes

Changelog

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

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

Commits


Updates @effect/printer from 0.33.24 to 0.33.26

Release notes

Sourced from @​effect/printer's releases.

@​effect/printer-ansi@​0.33.26

Patch Changes

@​effect/printer@​0.33.26

Patch Changes

@​effect/printer-ansi@​0.33.25

Patch Changes

@​effect/printer@​0.33.25

Patch Changes

Changelog

Sourced from @​effect/printer's changelog.

0.33.26

Patch Changes

0.33.25

Patch Changes

Commits


Updates @effect/printer-ansi from 0.33.24 to 0.33.26

Release notes

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

@​effect/printer-ansi@​0.33.26

Patch Changes

@​effect/printer-ansi@​0.33.25

Patch Changes

Changelog

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

0.33.26

Patch Changes

0.33.25

Patch Changes

Commits


Updates @effect/schema from 0.67.18 to 0.67.21

Release notes

Sourced from @​effect/schema's releases.

@​effect/schema@​0.67.21

Patch Changes

@​effect/schema@​0.67.20

Patch Changes

  • #2926 4c6bc7f Thanks @​gcanti! - Add propertyOrder option to ParseOptions to control the order of keys in the output, closes #2925.

    The propertyOrder option provides control over the order of object fields in the output. This feature is particularly useful when the sequence of keys is important for the consuming processes or when maintaining the input order enhances readability and usability.

    By default, the propertyOrder option is set to "none". This means that the internal system decides the order of keys to optimize parsing speed. The order of keys in this mode should not be considered stable, and it's recommended not to rely on key ordering as it may change in future updates without notice.

    Setting propertyOrder to "input" ensures that the keys are ordered as they appear in the input during the decoding/encoding process.

    Example (Synchronous Decoding)

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

    const schema = Schema.Struct({
a: Schema.Number,
b: Schema.Literal("b"),
c: Schema.Number,
});
    

    // Decoding an object synchronously without specifying the property order
console.log(Schema.decodeUnknownSync(schema)({ b: "b", c: 2, a: 1 }));
// Output decided internally: { b: 'b', a: 1, c: 2 }
    

    // Decoding an object synchronously while preserving the order of properties as in the input
console.log(
Schema.decodeUnknownSync(schema)(
{ b: "b", c: 2, a: 1 },
{ propertyOrder: "original" },
),
);
// Output preserving input order: { b: 'b', c: 2, a: 1 }

    Example (Asynchronous Decoding)

    import { ParseResult, Schema } from "@effect/schema";
import type { Duration } from "effect";
import { Effect } from "effect";

... (truncated)

Changelog

Sourced from @​effect/schema's changelog.

0.67.21

Patch Changes

0.67.20

Patch Changes

  • #2926 4c6bc7f Thanks @​gcanti! - Add propertyOrder option to ParseOptions to control the order of keys in the output, closes #2925.

    The propertyOrder option provides control over the order of object fields in the output. This feature is particularly useful when the sequence of keys is important for the consuming processes or when maintaining the input order enhances readability and usability.

    By default, the propertyOrder option is set to "none". This means that the internal system decides the order of keys to optimize parsing speed. The order of keys in this mode should not be considered stable, and it's recommended not to rely on key ordering as it may change in future updates without notice.

    Setting propertyOrder to "input" ensures that the keys are ordered as they appear in the input during the decoding/encoding process.

    Example (Synchronous Decoding)

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

    const schema = Schema.Struct({
a: Schema.Number,
b: Schema.Literal("b"),
c: Schema.Number,
});
    

    // Decoding an object synchronously without specifying the property order
console.log(Schema.decodeUnknownSync(schema)({ b: "b", c: 2, a: 1 }));
// Output decided internally: { b: 'b', a: 1, c: 2 }
    

    // Decoding an object synchronously while preserving the order of properties as in the input
console.log(
Schema.decodeUnknownSync(schema)(
{ b: "b", c: 2, a: 1 },
{ propertyOrder: "original" },
),
);
// Output preserving input order: { b: 'b', c: 2, a: 1 }

    Example (Asynchronous Decoding)

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

... (truncated)

Commits


Updates effect from 3.2.8 to 3.3.0

Release notes

Sourced from effect's releases.

effect@3.3.0

Minor Changes

  • #2837 1f4ac00 Thanks @​dilame! - add Stream.zipLatestAll api

  • #2837 9305b76 Thanks @​mattrossman! - Add queuing strategy option for Stream.toReadableStream

  • #2837 0f40d98 Thanks @​tim-smart! - add timeToLiveStrategy to Pool options

    The timeToLiveStrategy determines how items are invalidated. If set to "creation", then items are invalidated based on their creation time. If set to "usage", then items are invalidated based on pool usage.

    By default, the timeToLiveStrategy is set to "usage".

  • #2837 b761ef0 Thanks @​tim-smart! - add Layer.annotateLogs & Layer.annotateSpans

    This allows you to add log & span annotation to a Layer.

    import { Effect, Layer } from "effect";

    Layer.effectDiscard(Effect.log("hello")).pipe(
Layer.annotateLogs({
service: "my-service",
}),
);

  • #2837 b53f69b Thanks @​dilame! - Types: implement TupleOf and TupleOfAtLeast types

    Predicate: implement isTupleOf and isTupleOfAtLeast type guards

  • #2837 0f40d98 Thanks @​tim-smart! - add concurrency & targetUtilization option to Pool.make & Pool.makeWithTTL

    This option allows you to specify the level of concurrent access per pool item. I.e. setting concurrency: 2 will allow each pool item to be in use by 2 concurrent tasks.

    targetUtilization determines when to create new pool items. It is a value between 0 and 1, where 1 means only create new pool items when all the existing items are fully utilized.

    A targetUtilization of 0.5 will create new pool items when the existing items are 50% utilized.

  • #2837 5bd549e Thanks @​KhraksMamtsov! - Support this argument for {STM, Either, Option}.gen

  • #2837 67f160a Thanks @​KhraksMamtsov! - Introduced Redacted<out T = string> module - Secret generalization Secret extends Redacted The use of the Redacted has been replaced by the use of the Redacted in packages with version 0.*.*

... (truncated)

Changelog

Sourced from effect's changelog.

3.3.0

Minor Changes

  • #2837 1f4ac00 Thanks @​dilame! - add Stream.zipLatestAll api

  • #2837 9305b76 Thanks @​mattrossman! - Add queuing strategy option for Stream.toReadableStream

  • #2837 0f40d98 Thanks @​tim-smart! - add timeToLiveStrategy to Pool options

    The timeToLiveStrategy determines how items are invalidated. If set to "creation", then items are invalidated based on their creation time. If set to "usage", then items are invalidated based on pool usage.

    By default, the timeToLiveStrategy is set to "usage".

  • #2837 b761ef0 Thanks @​tim-smart! - add Layer.annotateLogs & Layer.annotateSpans

    This allows you to add log & span annotation to a Layer.

    import { Effect, Layer } from "effect";

    Layer.effectDiscard(Effect.log("hello")).pipe(
Layer.annotateLogs({
service: "my-service",
}),
);

  • #2837 b53f69b Thanks @​dilame! - Types: implement TupleOf and TupleOfAtLeast types

    Predicate: implement isTupleOf and isTupleOfAtLeast type guards

  • #2837 0f40d98 Thanks @​tim-smart! - add concurrency & targetUtilization option to Pool.make & Pool.makeWithTTL

    This option allows you to specify the level of concurrent access per pool item. I.e. setting concurrency: 2 will allow each pool item to be in use by 2 concurrent tasks.

    targetUtilization determines when to create new pool items. It is a value between 0 and 1, where 1 means only create new pool items when all the existing items are fully utilized.

    A targetUtilization of 0.5 will create new pool items when the existing items are 50% utilized.

  • #2837 5bd549e Thanks @​KhraksMamtsov! - Support this argument for {STM, Either, Option}.gen

  • #2837 67f160a Thanks @​KhraksMamtsov! - Introduced Redacted<out T = string> module - Secret generalization Secret extends Redacted

... (truncated)

Commits
dependabot[bot] commented 5 months ago

Superseded by #361.