chore(deps): update dependencies (non-major) #69

Merged

t.behrendt merged 1 commits from renovate/dependencies-(non-major) into main 2026-04-11 10:31:53 +02:00

Conversation 1 Commits 1 Files Changed 3 +516 -531

renovate-bot commented 2026-03-19 08:04:31 +01:00

Collaborator

Copy Link

This PR contains the following updates:

Package	Change	Age	Confidence
@types/node (source)	24.12.0 → 24.12.2
esbuild	0.27.3 → 0.28.0
jest (source)	30.2.0 → 30.3.0
ts-jest (source)	29.4.6 → 29.4.9

---

Release Notes

evanw/esbuild (esbuild)

v0.28.0

Compare Source

• Add support for with { type: 'text' } imports (#​4435)

  The import text proposal has reached stage 3 in the TC39 process, which means that it's recommended for implementation. It has also already been implemented by Deno and Bun. So with this release, esbuild also adds support for it. This behaves exactly the same as esbuild's existing text loader. Here's an example:

  import string from './example.txt' with { type: 'text' }
  console.log(string)
  

• Add integrity checks to fallback download path (#​4343)

  Installing esbuild via npm is somewhat complicated with several different edge cases (see esbuild's documentation for details). If the regular installation of esbuild's platform-specific package fails, esbuild's install script attempts to download the platform-specific package itself (first with the npm command, and then with a HTTP request to registry.npmjs.org as a last resort).

  This last resort path previously didn't have any integrity checks. With this release, esbuild will now verify that the hash of the downloaded binary matches the expected hash for the current release. This means the hashes for all of esbuild's platform-specific binary packages will now be embedded in the top-level esbuild package. Hopefully this should work without any problems. But just in case, this change is being done as a breaking change release.

• Update the Go compiler from 1.25.7 to 1.26.1

  This upgrade should not affect anything. However, there have been some significant internal changes to the Go compiler, so esbuild could potentially behave differently in certain edge cases:

  • It now uses the new garbage collector that comes with Go 1.26.
  • The Go compiler is now more aggressive with allocating memory on the stack.
  • The executable format that the Go linker uses has undergone several changes.
  • The WebAssembly build now unconditionally makes use of the sign extension and non-trapping floating-point to integer conversion instructions.

  You can read the Go 1.26 release notes for more information.

v0.27.7

Compare Source

• Fix lowering of define semantics for TypeScript parameter properties (#​4421)

  The previous release incorrectly generated class fields for TypeScript parameter properties even when the configured target environment does not support class fields. With this release, the generated class fields will now be correctly lowered in this case:

  // Original code
  class Foo {
    constructor(public x = 1) {}
    y = 2
  }
  
  // Old output (with --loader=ts --target=es2021)
  class Foo {
    constructor(x = 1) {
      this.x = x;
      __publicField(this, "y", 2);
    }
    x;
  }
  
  // New output (with --loader=ts --target=es2021)
  class Foo {
    constructor(x = 1) {
      __publicField(this, "x", x);
      __publicField(this, "y", 2);
    }
  }
  

v0.27.5

Compare Source

• Fix for an async generator edge case (#​4401, #​4417)

  Support for transforming async generators into the equivalent state machine was added in version 0.19.0. However, the generated state machine didn't work correctly when polling async generators concurrently, such as in the following code:

  async function* inner() { yield 1; yield 2 }
  async function* outer() { yield* inner() }
  let gen = outer()
  for await (let x of [gen.next(), gen.next()]) console.log(x)
  

  Previously esbuild's output of the above code behaved incorrectly when async generators were transformed (such as with --supported:async-generator=false). The transformation should be fixed starting with this release.

  This fix was contributed by @​2767mr.

• Fix a regression when metafile is enabled (#​4420, #​4418)

  This release fixes a regression introduced by the previous release. When metafile: true was enabled in esbuild's JavaScript API, builds with build errors were incorrectly throwing an error about an empty JSON string instead of an object containing the build errors.

• Use define semantics for TypeScript parameter properties (#​4421)

  Parameter properties are a TypeScript-specific code generation feature that converts constructor parameters into class fields when they are prefixed by certain keywords. When "useDefineForClassFields": true is present in tsconfig.json, the TypeScript compiler automatically generates class field declarations for parameter properties. Previously esbuild didn't do this, but esbuild will now do this starting with this release:

  // Original code
  class Foo {
    constructor(public x: number) {}
  }
  
  // Old output (with --loader=ts)
  class Foo {
    constructor(x) {
      this.x = x;
    }
  }
  
  // New output (with --loader=ts)
  class Foo {
    constructor(x) {
      this.x = x;
    }
    x;
  }
  

• Allow es2025 as a target in tsconfig.json (#​4432)

  TypeScript recently added es2025 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2025"
    }
  }
  

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

v0.27.4

Compare Source

• Fix a regression with CSS media queries (#​4395, #​4405, #​4406)

  Version 0.25.11 of esbuild introduced support for parsing media queries. This unintentionally introduced a regression with printing media queries that use the <media-type> and <media-condition-without-or> grammar. Specifically, esbuild was failing to wrap an or clause with parentheses when inside <media-condition-without-or>. This release fixes the regression.

  Here is an example:

  /* Original code */
  @​media only screen and ((min-width: 10px) or (min-height: 10px)) {
    a { color: red }
  }
  
  /* Old output (incorrect) */
  @​media only screen and (min-width: 10px) or (min-height: 10px) {
    a {
      color: red;
    }
  }
  
  /* New output (correct) */
  @​media only screen and ((min-width: 10px) or (min-height: 10px)) {
    a {
      color: red;
    }
  }
  

• Fix an edge case with the inject feature (#​4407)

  This release fixes an edge case where esbuild's inject feature could not be used with arbitrary module namespace names exported using an export {} from statement with bundling disabled and a target environment where arbitrary module namespace names is unsupported.

  With the fix, the following inject file:

  import jquery from 'jquery';
  export { jquery as 'window.jQuery' };
  

  Can now always be rewritten as this without esbuild sometimes incorrectly generating an error:

  export { default as 'window.jQuery' } from 'jquery';
  

• Attempt to improve API handling of huge metafiles (#​4329, #​4415)

  This release contains a few changes that attempt to improve the behavior of esbuild's JavaScript API with huge metafiles (esbuild's name for the build metadata, formatted as a JSON object). The JavaScript API is designed to return the metafile JSON as a JavaScript object in memory, which makes it easy to access from within a JavaScript-based plugin. Multiple people have encountered issues where this API breaks down with a pathologically-large metafile.

  The primary issue is that V8 has an implementation-specific maximum string length, so using the JSON.parse API with large enough strings is impossible. This release will now attempt to use a fallback JavaScript-based JSON parser that operates directly on the UTF8-encoded JSON bytes instead of using JSON.parse when the JSON metafile is too big to fit in a JavaScript string. The new fallback path has not yet been heavily-tested. The metafile will also now be generated with whitespace removed if the bundle is significantly large, which will reduce the size of the metafile JSON slightly.

  However, hitting this case is potentially a sign that something else is wrong. Ideally you wouldn't be building something so enormous that the build metadata can't even fit inside a JavaScript string. You may want to consider optimizing your project, or breaking up your project into multiple parts that are built independently. Another option could potentially be to use esbuild's command-line API instead of its JavaScript API, which is more efficient (although of course then you can't use JavaScript plugins, so it may not be an option).

jestjs/jest (jest)

v30.3.0

Compare Source

Features

• [jest-config] Add defineConfig and mergeConfig helpers for type-safe Jest config (#​15844)
• [jest-fake-timers] Add setTimerTickMode to configure how timers advance
• [*] Reduce token usage when run through LLMs (3f17932)

Fixes

• [jest-config] Keep CLI coverage output when using --json with --outputFile (#​15918)
• [jest-mock] Use Symbol from test environment (#​15858)
• [jest-reporters] Fix issue where console output not displayed for GHA reporter even with silent: false option (#​15864)
• [jest-runtime] Fix issue where user cannot utilize dynamic import despite specifying --experimental-vm-modules Node option (#​15842)
• [jest-test-sequencer] Fix issue where failed tests due to compilation errors not getting re-executed even with --onlyFailures CLI option (#​15851)
• [jest-util] Make sure process.features.require_module is false (#​15867)

Chore & Maintenance

• [*] Replace remaining micromatch uses with picomatch
• [deps] Update to sinon/fake-timers v15
• [docs] Update V30 migration guide to notify users on jest.mock() work with case-sensitive path (#​15849)
• Updated Twitter icon to match the latest brand guidelines (#​15869)

kulshekhar/ts-jest (ts-jest)

v29.4.9

Compare Source

Please refer to CHANGELOG.md for details.

v29.4.8

Compare Source

v29.4.7

Compare Source

Features

• support TypeScript v6 (eda517d)

---

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 Renovate Bot.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | [`24.12.0` → `24.12.2`](https://renovatebot.com/diffs/npm/@types%2fnode/24.12.0/24.12.2) |  |  | | [esbuild](https://github.com/evanw/esbuild) | [`0.27.3` → `0.28.0`](https://renovatebot.com/diffs/npm/esbuild/0.27.3/0.28.0) |  |  | | [jest](https://jestjs.io/) ([source](https://github.com/jestjs/jest/tree/HEAD/packages/jest)) | [`30.2.0` → `30.3.0`](https://renovatebot.com/diffs/npm/jest/30.2.0/30.3.0) |  |  | | [ts-jest](https://kulshekhar.github.io/ts-jest) ([source](https://github.com/kulshekhar/ts-jest)) | [`29.4.6` → `29.4.9`](https://renovatebot.com/diffs/npm/ts-jest/29.4.6/29.4.9) |  |  | --- ### Release Notes <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.28.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0280) [Compare Source](https://github.com/evanw/esbuild/compare/v0.27.7...v0.28.0) - Add support for `with { type: 'text' }` imports ([#&#8203;4435](https://github.com/evanw/esbuild/issues/4435)) The [import text](https://github.com/tc39/proposal-import-text) proposal has reached stage 3 in the TC39 process, which means that it's recommended for implementation. It has also already been implemented by [Deno](https://docs.deno.com/examples/importing_text/) and [Bun](https://bun.com/docs/guides/runtime/import-html). So with this release, esbuild also adds support for it. This behaves exactly the same as esbuild's existing [`text` loader](https://esbuild.github.io/content-types/#text). Here's an example: ```js import string from './example.txt' with { type: 'text' } console.log(string) ``` - Add integrity checks to fallback download path ([#&#8203;4343](https://github.com/evanw/esbuild/issues/4343)) Installing esbuild via npm is somewhat complicated with several different edge cases (see [esbuild's documentation](https://esbuild.github.io/getting-started/#additional-npm-flags) for details). If the regular installation of esbuild's platform-specific package fails, esbuild's install script attempts to download the platform-specific package itself (first with the `npm` command, and then with a HTTP request to `registry.npmjs.org` as a last resort). This last resort path previously didn't have any integrity checks. With this release, esbuild will now verify that the hash of the downloaded binary matches the expected hash for the current release. This means the hashes for all of esbuild's platform-specific binary packages will now be embedded in the top-level `esbuild` package. Hopefully this should work without any problems. But just in case, this change is being done as a breaking change release. - Update the Go compiler from 1.25.7 to 1.26.1 This upgrade should not affect anything. However, there have been some significant internal changes to the Go compiler, so esbuild could potentially behave differently in certain edge cases: - It now uses the [new garbage collector](https://go.dev/doc/go1.26#new-garbage-collector) that comes with Go 1.26. - The Go compiler is now more aggressive with allocating memory on the stack. - The executable format that the Go linker uses has undergone several changes. - The WebAssembly build now unconditionally makes use of the sign extension and non-trapping floating-point to integer conversion instructions. You can read the [Go 1.26 release notes](https://go.dev/doc/go1.26) for more information. ### [`v0.27.7`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0277) [Compare Source](https://github.com/evanw/esbuild/compare/v0.27.5...v0.27.7) - Fix lowering of define semantics for TypeScript parameter properties ([#&#8203;4421](https://github.com/evanw/esbuild/issues/4421)) The previous release incorrectly generated class fields for TypeScript parameter properties even when the configured target environment does not support class fields. With this release, the generated class fields will now be correctly lowered in this case: ```ts // Original code class Foo { constructor(public x = 1) {} y = 2 } // Old output (with --loader=ts --target=es2021) class Foo { constructor(x = 1) { this.x = x; __publicField(this, "y", 2); } x; } // New output (with --loader=ts --target=es2021) class Foo { constructor(x = 1) { __publicField(this, "x", x); __publicField(this, "y", 2); } } ``` ### [`v0.27.5`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0275) [Compare Source](https://github.com/evanw/esbuild/compare/v0.27.4...v0.27.5) - Fix for an async generator edge case ([#&#8203;4401](https://github.com/evanw/esbuild/issues/4401), [#&#8203;4417](https://github.com/evanw/esbuild/pull/4417)) Support for transforming async generators into the equivalent state machine was added in version 0.19.0. However, the generated state machine didn't work correctly when polling async generators concurrently, such as in the following code: ```js async function* inner() { yield 1; yield 2 } async function* outer() { yield* inner() } let gen = outer() for await (let x of [gen.next(), gen.next()]) console.log(x) ``` Previously esbuild's output of the above code behaved incorrectly when async generators were transformed (such as with `--supported:async-generator=false`). The transformation should be fixed starting with this release. This fix was contributed by [@&#8203;2767mr](https://github.com/2767mr). - Fix a regression when `metafile` is enabled ([#&#8203;4420](https://github.com/evanw/esbuild/issues/4420), [#&#8203;4418](https://github.com/evanw/esbuild/pull/4418)) This release fixes a regression introduced by the previous release. When `metafile: true` was enabled in esbuild's JavaScript API, builds with build errors were incorrectly throwing an error about an empty JSON string instead of an object containing the build errors. - Use define semantics for TypeScript parameter properties ([#&#8203;4421](https://github.com/evanw/esbuild/issues/4421)) Parameter properties are a TypeScript-specific code generation feature that converts constructor parameters into class fields when they are prefixed by certain keywords. When `"useDefineForClassFields": true` is present in `tsconfig.json`, the TypeScript compiler automatically generates class field declarations for parameter properties. Previously esbuild didn't do this, but esbuild will now do this starting with this release: ```ts // Original code class Foo { constructor(public x: number) {} } // Old output (with --loader=ts) class Foo { constructor(x) { this.x = x; } } // New output (with --loader=ts) class Foo { constructor(x) { this.x = x; } x; } ``` - Allow `es2025` as a target in `tsconfig.json` ([#&#8203;4432](https://github.com/evanw/esbuild/issues/4432)) TypeScript recently [added `es2025`](https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/#es2025-option-for-target-and-lib) as a compilation target, so esbuild now supports this in the `target` field of `tsconfig.json` files, such as in the following configuration file: ```json { "compilerOptions": { "target": "ES2025" } } ``` As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in [the documentation](https://esbuild.github.io/content-types/#tsconfig-json). ### [`v0.27.4`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0274) [Compare Source](https://github.com/evanw/esbuild/compare/v0.27.3...v0.27.4) - Fix a regression with CSS media queries ([#&#8203;4395](https://github.com/evanw/esbuild/issues/4395), [#&#8203;4405](https://github.com/evanw/esbuild/issues/4405), [#&#8203;4406](https://github.com/evanw/esbuild/issues/4406)) Version 0.25.11 of esbuild introduced support for parsing media queries. This unintentionally introduced a regression with printing media queries that use the `<media-type> and <media-condition-without-or>` grammar. Specifically, esbuild was failing to wrap an `or` clause with parentheses when inside `<media-condition-without-or>`. This release fixes the regression. Here is an example: ```css /* Original code */ @&#8203;media only screen and ((min-width: 10px) or (min-height: 10px)) { a { color: red } } /* Old output (incorrect) */ @&#8203;media only screen and (min-width: 10px) or (min-height: 10px) { a { color: red; } } /* New output (correct) */ @&#8203;media only screen and ((min-width: 10px) or (min-height: 10px)) { a { color: red; } } ``` - Fix an edge case with the `inject` feature ([#&#8203;4407](https://github.com/evanw/esbuild/issues/4407)) This release fixes an edge case where esbuild's `inject` feature could not be used with arbitrary module namespace names exported using an `export {} from` statement with bundling disabled and a target environment where arbitrary module namespace names is unsupported. With the fix, the following `inject` file: ```js import jquery from 'jquery'; export { jquery as 'window.jQuery' }; ``` Can now always be rewritten as this without esbuild sometimes incorrectly generating an error: ```js export { default as 'window.jQuery' } from 'jquery'; ``` - Attempt to improve API handling of huge metafiles ([#&#8203;4329](https://github.com/evanw/esbuild/issues/4329), [#&#8203;4415](https://github.com/evanw/esbuild/issues/4415)) This release contains a few changes that attempt to improve the behavior of esbuild's JavaScript API with huge metafiles (esbuild's name for the build metadata, formatted as a JSON object). The JavaScript API is designed to return the metafile JSON as a JavaScript object in memory, which makes it easy to access from within a JavaScript-based plugin. Multiple people have encountered issues where this API breaks down with a pathologically-large metafile. The primary issue is that V8 has an implementation-specific maximum string length, so using the `JSON.parse` API with large enough strings is impossible. This release will now attempt to use a fallback JavaScript-based JSON parser that operates directly on the UTF8-encoded JSON bytes instead of using `JSON.parse` when the JSON metafile is too big to fit in a JavaScript string. The new fallback path has not yet been heavily-tested. The metafile will also now be generated with whitespace removed if the bundle is significantly large, which will reduce the size of the metafile JSON slightly. However, hitting this case is potentially a sign that something else is wrong. Ideally you wouldn't be building something so enormous that the build metadata can't even fit inside a JavaScript string. You may want to consider optimizing your project, or breaking up your project into multiple parts that are built independently. Another option could potentially be to use esbuild's command-line API instead of its JavaScript API, which is more efficient (although of course then you can't use JavaScript plugins, so it may not be an option). </details> <details> <summary>jestjs/jest (jest)</summary> ### [`v30.3.0`](https://github.com/jestjs/jest/blob/HEAD/CHANGELOG.md#3030) [Compare Source](https://github.com/jestjs/jest/compare/v30.2.0...v30.3.0) ##### Features - `[jest-config]` Add `defineConfig` and `mergeConfig` helpers for type-safe Jest config ([#&#8203;15844](https://github.com/jestjs/jest/pull/15844)) - `[jest-fake-timers]` Add `setTimerTickMode` to configure how timers advance - `[*]` Reduce token usage when run through LLMs ([`3f17932`](https://github.com/jestjs/jest/commit/3f17932061c0203999451e5852664093de876709)) ##### Fixes - `[jest-config]` Keep CLI coverage output when using `--json` with `--outputFile` ([#&#8203;15918](https://github.com/jestjs/jest/pull/15918)) - `[jest-mock]` Use `Symbol` from test environment ([#&#8203;15858](https://github.com/jestjs/jest/pull/15858)) - `[jest-reporters]` Fix issue where console output not displayed for GHA reporter even with `silent: false` option ([#&#8203;15864](https://github.com/jestjs/jest/pull/15864)) - `[jest-runtime]` Fix issue where user cannot utilize dynamic import despite specifying `--experimental-vm-modules` Node option ([#&#8203;15842](https://github.com/jestjs/jest/pull/15842)) - `[jest-test-sequencer]` Fix issue where failed tests due to compilation errors not getting re-executed even with `--onlyFailures` CLI option ([#&#8203;15851](https://github.com/jestjs/jest/pull/15851)) - `[jest-util]` Make sure `process.features.require_module` is `false` ([#&#8203;15867](https://github.com/jestjs/jest/pull/15867)) ##### Chore & Maintenance - `[*]` Replace remaining micromatch uses with picomatch - `[deps]` Update to sinon/fake-timers v15 - `[docs]` Update V30 migration guide to notify users on `jest.mock()` work with case-sensitive path ([#&#8203;15849](https://github.com/jestjs/jest/pull/15849)) - Updated Twitter icon to match the latest brand guidelines ([#&#8203;15869](https://github.com/jestjs/jest/pull/15869)) </details> <details> <summary>kulshekhar/ts-jest (ts-jest)</summary> ### [`v29.4.9`](https://github.com/kulshekhar/ts-jest/releases/tag/v29.4.9) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.4.8...v29.4.9) Please refer to [CHANGELOG.md](https://github.com/kulshekhar/ts-jest/blob/main/CHANGELOG.md) for details. ### [`v29.4.8`](https://github.com/kulshekhar/ts-jest/compare/v29.4.7...v29.4.8) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.4.7...v29.4.8) ### [`v29.4.7`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2947-2026-04-01) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.4.6...v29.4.7) ##### Features - support TypeScript v6 ([eda517d](https://github.com/kulshekhar/ts-jest/commit/eda517d226389317d99572887d3c1aa93c81be87)) </details> --- ### 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](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My41LjQiLCJ1cGRhdGVkSW5WZXIiOiI0My41LjQiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->

renovate-bot changed title from chore(deps): update dependency jest to v30.3.0 to chore(deps): update dependencies (non-major) 2026-03-20 11:16:52 +01:00

renovate-bot added 1 commit 2026-04-10 13:27:27 +02:00

chore(deps): update dependencies (non-major) b2dfaef432

renovate-bot force-pushed renovate/dependencies-(non-major) from d7305b395f to b2dfaef432 2026-04-10 13:27:27 +02:00 Compare

t.behrendt approved these changes 2026-04-11 10:31:50 +02:00

t.behrendt merged commit 74d41d9bd9 into main 2026-04-11 10:31:53 +02:00

t.behrendt deleted branch renovate/dependencies-(non-major) 2026-04-11 10:31:53 +02:00

t.behrendt referenced this issue from a commit 2026-04-11 10:31:55 +02:00

chore(deps): update dependencies (non-major) (#69)

Sign in to join this conversation.

Reviewers

No Reviewers

t.behrendt

Labels

Clear labels

bug

Something is not working

duplicate

This issue or pull request already exists

enhancement

New feature

help wanted

Need some help

invalid

Something is wrong

question

More information is needed

wontfix

This won't be fixed

No Label

Milestone

No items

No Milestone

Assignees

Clear assignees

renovate-bot t.behrendt

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: t.behrendt/conventional-semantic-git-tag-increment#69