kjuulh/vidow
1
0
Fork 0
Code Issues 1 Pull Requests 3 Packages Projects Releases Wiki Activity

Update all dependencies #451

Open
kjuulh wants to merge 1 commits from renovate/all into main
pull from: renovate/all
merge into: kjuulh:main
Conversation 0 Commits 1 Files Changed 3 +50 -32
kjuulh commented 2025-03-26 00:25:40 +01:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
@reduxjs/toolkit (source) dependencies minor 2.6.0 -> 2.7.0
@types/node (source) devDependencies minor 22.13.9 -> 22.14.1
clap dependencies patch 4.5.31 -> 4.5.37
ts-jest (source) devDependencies minor 29.2.6 -> 29.3.2
typescript (source) devDependencies patch 5.8.2 -> 5.8.3

Release Notes

reduxjs/redux-toolkit (@​reduxjs/toolkit)

v2.7.0

Compare Source

RTK has hit Stage 2.7! 🤣 This feature release adds support for Standard Schema validation in RTK Query endpoints, fixes several issues with infinite queries, improves perf when infinite queries provide tags, adds a dev-mode check for duplicate middleware, and improves reference stability in slice selectors and infinite query hooks.

Changelog

Standard Schema Validation for RTK Query

Apps often need to validate responses from the server, both to ensure the data is correct, and to help enforce that the data matches the expected TS types. This is typically done with schema libraries such as Zod, Valibot, and Arktype. Because of the similarities in usage APIs, those libraries and others now support a common API definition called Standard Schema, allowing you to plug your chosen validation library in anywhere Standard Schema is supported.

RTK Query now supports using Standard Schema to validate query args, responses, and errors. If schemas are provided, the validations will be run and errors thrown if the data is invalid. Additionally, providing a schema allows TS inference for that type as well, allowing you to omit generic types from the endpoint.

Schema usage is per-endpoint, and can look like this:

import { createApi, fetchBaseQuery } from '@​reduxjs/toolkit/query/react'
import * as v from 'valibot'

const postSchema = v.object({
  id: v.number(),
  name: v.string(),
})
type Post = v.InferOutput<typeof postSchema>

const api = createApi({
  baseQuery: fetchBaseQuery({ baseUrl: '/' }),
  endpoints: (build) => ({
    getPost: build.query({
      // infer arg from here
      query: ({ id }: { id: number }) => `/post/${id}`,
      // infer result from here
      responseSchema: postSchema,
    }),
    getTransformedPost: build.query({
      // infer arg from here
      query: ({ id }: { id: number }) => `/post/${id}`,
      // infer untransformed result from here
      rawResponseSchema: postSchema,
      // infer transformed result from here
      transformResponse: (response) => ({
        ...response,
        published_at: new Date(response.published_at),
      }),
    }),
  }),
})

If desired, you can also configure schema error handling with the catchSchemaFailure option. You can also disable actual runtime validation with skipSchemaValidation (primarily useful for cases when payloads may be large and expensive to validate, but you still want to benefit from the TS type inference).

See the "Schema Validation" docs section in the createApi reference and the usage guide sections on queries, infinite queries, and mutations, for more details.

Infinite Query Fixes

This release fixes several reported issue with infinite queries:

  • The lifecycleApi.updateCachedData method is now correctly available
  • The skip option now correctly works for infinite query hooks
  • Infinite query fulfilled actions now include the meta field from the base query (such as {request, response}). For cases where multiple pages are being refetched, this will be the meta from the last page fetched.
  • useInfiniteQuerySubscription now returns stable references for refetch and the fetchNext/PreviousPage methods
upsertQueryEntries, Tags Performance and API State Structure

We recently published a fix to actually process per-endpoint providedTags when using upsertQueryEntries. However, this exposed a performance issue - the internal tag handling logic was doing repeated O(n) iterations over all endpoint+tag entries in order to clear out existing references to that cache key. In cases where hundreds or thousands of cache entries were being inserted, this became extremely expensive.

We've restructured the state.api.provided data structure to handle reverse-mapping between tags and cache keys, which drastically improves performance in this case. However, it's worth noting that this is a change to that state structure. This shouldn't affect apps, because the RTKQ state is intended to be treated as a black box and not generally directly accessed by user app code. However, it's possible someone may have depended on that specific state structure when writing a custom selector, in which case this would break. An actual example of this is the Redux DevTools RTKQ panel, which iterates the tags data while displaying cache entries. That did break with this change. Prior to releasing RTK 2.7,we released Redux DevTools 3.2.10, which includes support for both the old and new state.api.provided definitions.

TS Support Matrix Updates

Following with the DefinitelyTyped support matrix, we've officially dropped support for TS 5.0, and currently support TS 5.1 - 5.8. (RTK likely still works with 5.0, but we no longer test against that in CI.)

Duplicate Middleware Dev Checks

configureStore now checks the final middleware array for duplicate middleware references. This will catch cases such as accidentally adding the same RTKQ API middleware twice (such as adding baseApi.middleware and injectedApi.middlweware - these are actually the same object and same middleware).

Unlike the other dev-mode checks, this is part of configureStore itself, not getDefaultMiddleware().

This can be configured via the new duplicateMiddlewareCheck option.

Other Changes

createEntityAdapter now correctly handles adding an item and then applying multiple updates to it.

The generated combineSlices selectors will now return the same placeholder initial state reference for a given slice, rather than returning a new initial state reference every time.

useQuery hooks should now correctly refetch after dispatching resetApiState.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.6.1...v2.7.0

v2.6.1

Compare Source

This bugfix release fixes several assorted types issues with the initial infinite query feature release, and adds support for an optional signal argument to createAsyncThunk.

Changelog

Infinite Query Fixes

We've fixed several types issues that were reported with infinite queries after the 2.6.0 release:

  • matchFulfilled and providesTags now get the correct response types
  • We've added pre-typed Type* types to represent infinite queries, similar to the existing pre-defined types for queries and mutations
  • selectCachedArgsForQuery now supports fetching args for infinite query endpoints
  • We fixed some TS type portability issues with infinite queries that caused errors when generating TS declarations
  • useInfiniteQueryState/Subscription now correctly expect just the query arg, not the combined {queryArg, pageParam} object
Other Improvements

createAsyncThunk now accepts an optional {signal} argument. If provided, the internal AbortSignal handling will tie into that signal.

upsertQueryEntries now correctly generates provided tags for upserted cache entries.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.6.0...v2.6.1

clap-rs/clap (clap)

v4.5.37

Compare Source

Features
  • Added ArgMatches::try_clear_id()

v4.5.36

Compare Source

Fixes
  • (help) Revert 4.5.35's "Don't leave space for shorts if there are none" for now

v4.5.35

Compare Source

Fixes
  • (help) Align positionals and flags when put in the same help_heading
  • (help) Don't leave space for shorts if there are none

v4.5.34

Compare Source

Fixes
  • (help) Don't add extra blank lines with flatten_help(true) and subcommands without arguments

v4.5.33

Compare Source

Fixes
  • (error) When showing the usage of a suggestion for an unknown argument, don't show the group

v4.5.32

Compare Source

Features
  • Add Error::remove
Documentation
  • (cookbook) Switch from humantime to jiff
  • (tutorial) Better cover required vs optional
Internal
  • Update pulldown-cmark
kulshekhar/ts-jest (ts-jest)

v29.3.2

Compare Source

Bug Fixes
  • fix: transpile js files from node_modules whenever Jest asks (968370e), closes #​4637

v29.3.1

Compare Source

Bug Fixes
  • fix: allow isolatedModules mode to have ts.Program under Node16/Next (25157eb)
  • fix: improve message for isolatedModules of ts-jest config (547eb6f)

v29.3.0

Compare Source

Features
  • feat: support hybrid module values for isolatedModules: true (f372121)
Bug Fixes
  • fix: set customConditions to undefined in TsCompiler (b091d70), closes #​4620
Code Refactoring
  • refactor: remove manual version checker (89458fc)
  • refactor: remove patching deps based on version checker (bac4c43)
  • refactor: deprecate RawCompilerOptions interface (2b1b6cd)
  • refactor: deprecate transform option isolatedModules (7dfef71)
microsoft/TypeScript (typescript)

v5.8.3: TypeScript 5.8.3

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

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.

👻 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 | Type | Update | Change | |---|---|---|---| | [@reduxjs/toolkit](https://redux-toolkit.js.org) ([source](https://github.com/reduxjs/redux-toolkit)) | dependencies | minor | [`2.6.0` -> `2.7.0`](https://renovatebot.com/diffs/npm/@reduxjs%2ftoolkit/2.6.0/2.7.0) | | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | devDependencies | minor | [`22.13.9` -> `22.14.1`](https://renovatebot.com/diffs/npm/@types%2fnode/22.13.9/22.14.1) | | [clap](https://github.com/clap-rs/clap) | dependencies | patch | `4.5.31` -> `4.5.37` | | [ts-jest](https://kulshekhar.github.io/ts-jest) ([source](https://github.com/kulshekhar/ts-jest)) | devDependencies | minor | [`29.2.6` -> `29.3.2`](https://renovatebot.com/diffs/npm/ts-jest/29.2.6/29.3.2) | | [typescript](https://www.typescriptlang.org/) ([source](https://github.com/microsoft/TypeScript)) | devDependencies | patch | [`5.8.2` -> `5.8.3`](https://renovatebot.com/diffs/npm/typescript/5.8.2/5.8.3) | --- ### Release Notes <details> <summary>reduxjs/redux-toolkit (@&#8203;reduxjs/toolkit)</summary> ### [`v2.7.0`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.7.0) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.6.1...v2.7.0) RTK has hit Stage 2.7! :rofl: This **feature release** adds support for Standard Schema validation in RTK Query endpoints, fixes several issues with infinite queries, improves perf when infinite queries provide tags, adds a dev-mode check for duplicate middleware, and improves reference stability in slice selectors and infinite query hooks. #### Changelog ##### Standard Schema Validation for RTK Query Apps often need to validate responses from the server, both to ensure the data is correct, and to help enforce that the data matches the expected TS types. This is typically done with schema libraries such as Zod, Valibot, and Arktype. Because of the similarities in usage APIs, those libraries and others now support a common API definition called [Standard Schema](https://standardschema.dev/), allowing you to plug your chosen validation library in anywhere Standard Schema is supported. RTK Query now supports using Standard Schema to validate query args, responses, and errors. If schemas are provided, the validations will be run and errors thrown if the data is invalid. Additionally, providing a schema allows TS inference for that type as well, allowing you to omit generic types from the endpoint. Schema usage is per-endpoint, and can look like this: ```ts import { createApi, fetchBaseQuery } from '@&#8203;reduxjs/toolkit/query/react' import * as v from 'valibot' const postSchema = v.object({ id: v.number(), name: v.string(), }) type Post = v.InferOutput<typeof postSchema> const api = createApi({ baseQuery: fetchBaseQuery({ baseUrl: '/' }), endpoints: (build) => ({ getPost: build.query({ // infer arg from here query: ({ id }: { id: number }) => `/post/${id}`, // infer result from here responseSchema: postSchema, }), getTransformedPost: build.query({ // infer arg from here query: ({ id }: { id: number }) => `/post/${id}`, // infer untransformed result from here rawResponseSchema: postSchema, // infer transformed result from here transformResponse: (response) => ({ ...response, published_at: new Date(response.published_at), }), }), }), }) ``` If desired, you can also configure schema error handling with the `catchSchemaFailure` option. You can also disable actual runtime validation with `skipSchemaValidation` (primarily useful for cases when payloads may be large and expensive to validate, but you still want to benefit from the TS type inference). See the ["Schema Validation" docs section in the `createApi` reference](https://redux-toolkit.js.org/rtk-query/api/createApi#schema-validation) and the usage guide sections on [queries](https://redux-toolkit.js.org/rtk-query/usage/queries#runtime-validation-using-schemas), infinite queries, and mutations, for more details. ##### Infinite Query Fixes This release fixes several reported issue with infinite queries: - The `lifecycleApi.updateCachedData` method is now correctly available - The `skip` option now correctly works for infinite query hooks - Infinite query `fulfilled` actions now include the `meta` field from the base query (such as `{request, response}`). For cases where multiple pages are being refetched, this will be the meta from the last page fetched. - `useInfiniteQuerySubscription` now returns stable references for `refetch` and the `fetchNext/PreviousPage` methods ##### `upsertQueryEntries`, Tags Performance and API State Structure We recently published a fix to actually process per-endpoint `providedTags` when using `upsertQueryEntries`. However, this exposed a performance issue - the internal tag handling logic was doing repeated O(n) iterations over *all* endpoint+tag entries in order to clear out existing references to that cache key. In cases where hundreds or thousands of cache entries were being inserted, this became extremely expensive. We've restructured the `state.api.provided` data structure to handle reverse-mapping between tags and cache keys, which drastically improves performance in this case. However, it's worth noting that this *is* a change to that state structure. This *shouldn't* affect apps, because the RTKQ state is intended to be treated as a black box and not generally directly accessed by user app code. However, it's possible someone may have depended on that specific state structure when writing a custom selector, in which case this would break. An actual example of this is the Redux DevTools RTKQ panel, which iterates the tags data while displaying cache entries. That *did* break with this change. Prior to releasing RTK 2.7,we released [Redux DevTools 3.2.10](https://github.com/reduxjs/redux-devtools/releases/tag/remotedev-redux-devtools-extensions%403.2.10), which includes support for both the old and new `state.api.provided` definitions. ##### TS Support Matrix Updates Following with the DefinitelyTyped support matrix, we've officially dropped support for TS 5.0, and currently support TS 5.1 - 5.8. (RTK likely still works with 5.0, but we no longer test against that in CI.) ##### Duplicate Middleware Dev Checks `configureStore` now checks the final middleware array for duplicate middleware references. This will catch cases such as accidentally adding the same RTKQ API middleware twice (such as adding `baseApi.middleware` and `injectedApi.middlweware` - these are actually the same object and same middleware). Unlike the other dev-mode checks, this is part of `configureStore` itself, not `getDefaultMiddleware()`. This can be configured via the new `duplicateMiddlewareCheck` option. ##### Other Changes `createEntityAdapter` now correctly handles adding an item and then applying multiple updates to it. The generated `combineSlices` selectors will now return the same placeholder initial state reference for a given slice, rather than returning a new initial state reference every time. `useQuery` hooks should now correctly refetch after dispatching `resetApiState`. #### What's Changed - Process multiple update for the same new entity by [@&#8203;demyanm](https://github.com/demyanm) in https://github.com/reduxjs/redux-toolkit/pull/4890 - add infinite query support for updateCachedData by [@&#8203;alexmotoc](https://github.com/alexmotoc) in https://github.com/reduxjs/redux-toolkit/pull/4905 - add infinite query skip support by [@&#8203;alexmotoc](https://github.com/alexmotoc) in https://github.com/reduxjs/redux-toolkit/pull/4906 - Cache initial state in injected scenarios by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4908 - Rewrite providedTags handling for better perf by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4910 - Allow standard schemas to validate endpoint values by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4864 - fix(rtk-query): `useQuery` hook does not refetch after `resetApiState` by [@&#8203;juniusfree](https://github.com/juniusfree) in https://github.com/reduxjs/redux-toolkit/pull/4758 - Drop TS 5.0 from compat matrix by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4925 - Add duplicate middleware dev check to configureStore by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4927 - Improve duplicate middleware error and save build output by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4928 - Add meta handling for infinite queries by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4939 - improve stability of useInfiniteQuerySubscription's return value by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4937 - Add `catchSchemaFailure`, and docs for RTKQ schema features by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4934 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.6.1...v2.7.0 ### [`v2.6.1`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.6.1) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.6.0...v2.6.1) This **bugfix release** fixes several assorted types issues with the initial infinite query feature release, and adds support for an optional signal argument to `createAsyncThunk`. #### Changelog ##### Infinite Query Fixes We've fixed several types issues that were reported with infinite queries after the 2.6.0 release: - `matchFulfilled` and `providesTags` now get the correct response types - We've added pre-typed `Type*` types to represent infinite queries, similar to the existing pre-defined types for queries and mutations - `selectCachedArgsForQuery` now supports fetching args for infinite query endpoints - We fixed some TS type portability issues with infinite queries that caused errors when generating TS declarations - `useInfiniteQueryState/Subscription` now correctly expect just the query arg, not the combined `{queryArg, pageParam}` object ##### Other Improvements `createAsyncThunk` now accepts an optional `{signal}` argument. If provided, the internal AbortSignal handling will tie into that signal. `upsertQueryEntries` now correctly generates provided tags for upserted cache entries. #### What's Changed - Fix assorted infinite query types by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4869 - Add providesTags handling for upsertQueryEntries by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4872 - add infinite query type support for selectCachedArgsForQuery by [@&#8203;alexmotoc](https://github.com/alexmotoc) in https://github.com/reduxjs/redux-toolkit/pull/4880 - add more Typed wrappers and make sure they're all exported by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4866 - Fix infinite query type portability issues by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4881 - support passing an external abortsignal to createAsyncThunk by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4860 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.6.0...v2.6.1 </details> <details> <summary>clap-rs/clap (clap)</summary> ### [`v4.5.37`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4537---2025-04-18) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.36...v4.5.37) ##### Features - Added `ArgMatches::try_clear_id()` ### [`v4.5.36`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4536---2025-04-11) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.35...v4.5.36) ##### Fixes - *(help)* Revert 4.5.35's "Don't leave space for shorts if there are none" for now ### [`v4.5.35`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4535---2025-04-01) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.34...v4.5.35) ##### Fixes - *(help)* Align positionals and flags when put in the same `help_heading` - *(help)* Don't leave space for shorts if there are none ### [`v4.5.34`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4534---2025-03-27) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.33...v4.5.34) ##### Fixes - *(help)* Don't add extra blank lines with `flatten_help(true)` and subcommands without arguments ### [`v4.5.33`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4533---2025-03-26) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.32...v4.5.33) ##### Fixes - *(error)* When showing the usage of a suggestion for an unknown argument, don't show the group ### [`v4.5.32`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4532---2025-03-10) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.31...v4.5.32) ##### Features - Add `Error::remove` ##### Documentation - *(cookbook)* Switch from `humantime` to `jiff` - *(tutorial)* Better cover required vs optional ##### Internal - Update `pulldown-cmark` </details> <details> <summary>kulshekhar/ts-jest (ts-jest)</summary> ### [`v29.3.2`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2932-2025-04-12) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.3.1...v29.3.2) ##### Bug Fixes - fix: transpile `js` files from `node_modules` whenever Jest asks ([968370e](https://github.com/kulshekhar/ts-jest/commit/968370e)), closes [#&#8203;4637](https://github.com/kulshekhar/ts-jest/issues/4637) ### [`v29.3.1`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2931-2025-03-31) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.3.0...v29.3.1) ##### Bug Fixes - fix: allow `isolatedModules` mode to have `ts.Program` under `Node16/Next` ([25157eb](https://github.com/kulshekhar/ts-jest/commit/25157eb)) - fix: improve message for `isolatedModules` of `ts-jest` config ([547eb6f](https://github.com/kulshekhar/ts-jest/commit/547eb6f)) ### [`v29.3.0`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2930-2025-03-21) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.2.6...v29.3.0) ##### Features - feat: support hybrid `module` values for `isolatedModules: true` ([f372121](https://github.com/kulshekhar/ts-jest/commit/f372121)) ##### Bug Fixes - fix: set `customConditions` to `undefined` in `TsCompiler` ([b091d70](https://github.com/kulshekhar/ts-jest/commit/b091d70)), closes [#&#8203;4620](https://github.com/kulshekhar/ts-jest/issues/4620) ##### Code Refactoring - refactor: remove manual version checker ([89458fc](https://github.com/kulshekhar/ts-jest/commit/89458fc)) - refactor: remove patching deps based on version checker ([bac4c43](https://github.com/kulshekhar/ts-jest/commit/bac4c43)) - refactor: deprecate `RawCompilerOptions` interface ([2b1b6cd](https://github.com/kulshekhar/ts-jest/commit/2b1b6cd)) - refactor: deprecate transform option `isolatedModules` ([7dfef71](https://github.com/kulshekhar/ts-jest/commit/7dfef71)) </details> <details> <summary>microsoft/TypeScript (typescript)</summary> ### [`v5.8.3`](https://github.com/microsoft/TypeScript/releases/tag/v5.8.3): TypeScript 5.8.3 [Compare Source](https://github.com/microsoft/TypeScript/compare/v5.8.2...v5.8.3) For release notes, check out the [release announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-5-8/). - [fixed issues query for Typescript 5.8.0 (Beta)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.8.0%22+is%3Aclosed+). - [fixed issues query for Typescript 5.8.1 (RC)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.8.1%22+is%3Aclosed+). - [fixed issues query for Typescript 5.8.2 (Stable)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.8.2%22+is%3Aclosed+). - [fixed issues query for Typescript 5.8.3 (Stable)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.8.3%22+is%3Aclosed+). Downloads are available on: - [npm](https://www.npmjs.com/package/typescript) </details> --- ### 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. 👻 **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:eyJjcmVhdGVkSW5WZXIiOiIzOS4yMTUuMiIsInVwZGF0ZWRJblZlciI6IjM5LjI1MS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
kjuulh added 1 commit 2025-03-26 00:25:40 +01:00
kjuulh force-pushed renovate/all from 20f7c5ff1c to 262e6bc3ae 2025-03-26 20:49:24 +01:00 Compare
kjuulh force-pushed renovate/all from 262e6bc3ae to cc5c60c7c3 2025-03-26 21:22:20 +01:00 Compare
kjuulh force-pushed renovate/all from cc5c60c7c3 to 44d610cfe7 2025-03-27 02:50:04 +01:00 Compare
kjuulh force-pushed renovate/all from 44d610cfe7 to 7b90be6a0d 2025-03-27 03:22:23 +01:00 Compare
kjuulh force-pushed renovate/all from 7b90be6a0d to 9fd566308f 2025-03-27 04:56:31 +01:00 Compare
kjuulh force-pushed renovate/all from 9fd566308f to 377846d555 2025-04-01 02:48:53 +02:00 Compare
kjuulh force-pushed renovate/all from 377846d555 to 943b34be77 2025-04-02 02:54:17 +02:00 Compare
kjuulh force-pushed renovate/all from 943b34be77 to d83335f49b 2025-04-03 02:51:50 +02:00 Compare
kjuulh force-pushed renovate/all from d83335f49b to 7b6b189662 2025-04-05 02:49:47 +02:00 Compare
kjuulh force-pushed renovate/all from 7b6b189662 to 9481e452ff 2025-04-12 02:55:07 +02:00 Compare
kjuulh force-pushed renovate/all from 9481e452ff to d7b1f830ec 2025-04-14 02:48:45 +02:00 Compare
kjuulh force-pushed renovate/all from d7b1f830ec to ba88705f7c 2025-04-17 02:47:50 +02:00 Compare
kjuulh force-pushed renovate/all from ba88705f7c to 05537190b5 2025-04-19 02:51:30 +02:00 Compare
kjuulh force-pushed renovate/all from 05537190b5 to df260e7982 2025-04-19 05:48:51 +02:00 Compare
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/all:renovate/all
git checkout renovate/all
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kjuulh
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kjuulh/vidow#451
No description provided.
Delete Branch "renovate/all"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?