(chore): Bump the ci-dependencies group with 4 updates

[dependabot]

Bumps the ci-dependencies group with 4 updates: @redhat-cloud-services/frontend-components-notifications, @reduxjs/toolkit, globals and prettier.

Updates @redhat-cloud-services/frontend-components-notifications from 4.1.19 to 4.1.20

Release notes

Sourced from @​redhat-cloud-services/frontend-components-notifications's releases.

@​redhat-cloud-services/frontend-components-notifications-4.1.20

Changelog

This file was generated using @​jscutlery/semver.

4.1.20 (2025-02-19)

Dependency Updates

• @redhat-cloud-services/frontend-components updated to version 5.2.9

4.1.19 (2025-02-14)

Dependency Updates

• @redhat-cloud-services/frontend-components updated to version 5.2.8

4.1.18 (2025-02-14)

Dependency Updates

• @redhat-cloud-services/frontend-components updated to version 5.2.7

4.1.17 (2025-02-11)

Dependency Updates

• @redhat-cloud-services/frontend-components updated to version 5.2.6

4.1.16 (2025-02-10)

Dependency Updates

• @redhat-cloud-services/frontend-components-utilities updated to version 5.0.11
• @redhat-cloud-services/frontend-components updated to version 5.2.5

Bug Fixes

• add version ranges for react-redux 8.x.x and 9.x.x (#2159) (5d32d44)

4.1.15 (2025-02-07)

Dependency Updates

• @redhat-cloud-services/frontend-components updated to version 5.2.4

4.1.14 (2025-01-28)

Dependency Updates

• @redhat-cloud-services/frontend-components-utilities updated to version 5.0.10
• @redhat-cloud-services/frontend-components updated to version 5.2.3

4.1.13 (2025-01-28)

Dependency Updates

... (truncated)

Commits

• 9b1976b chore: bump @​redhat-cloud-services/frontend-components-notifications to 4.1.2...
• c87c13f chore: bump @​redhat-cloud-services/frontend-components to 5.2.9 [skip ci]
• a625dec Merge pull request #2171 from xmicha82/shield-spacing
• d04296a fix(Shield): fix shield spacing without QuestionIcon
• f544ca8 chore: bump @​redhat-cloud-services/frontend-components-advisor-components to ...
• 9666b75 chore: bump @​redhat-cloud-services/rule-components to 3.2.27 [skip ci]
• 565fbbd chore: bump @​redhat-cloud-services/frontend-components-remediations to 3.2.30...
• See full diff in compare view

Updates @reduxjs/toolkit from 2.5.1 to 2.6.0

Release notes

Sourced from @​reduxjs/toolkit's releases.

v2.6.0

This feature release adds infinite query support to RTK Query.

Changelog

RTK Query Infinite Query support

Since we first released RTK Query in 2021, we've had users asking us to add support for "infinite queries" - the ability to keep fetching additional pages of data for a given endpoint. It's been by far our most requested feature. Until recently, our answer was that we felt there were too many use cases to support with a single API design approach.

Last year, we revisited this concept and concluded that the best approach was to mimic the flexible infinite query API design from React Query. We had additional discussions with @​tkdodo , who described the rationale and implementation approach and encouraged us to use their API design, and @​riqts provided an initial implementation on top of RTKQ's existing internals.

We're excited to announce that this release officially adds full infinite query endpoint support to RTK Query!

Using Infinite Queries

As with React Query, the API design is based around "page param" values that act as the query arguments for fetching a specific page for the given cache entry.

Infinite queries are defined with a new build.infiniteQuery() endpoint type. It accepts all of the same options as normal query endpoints, but also needs an additional infiniteQueryOptions field that specifies the infinite query behaviors. With TypeScript, you must supply 3 generic arguments: build.infiniteQuery<ResultType, QueryArg, PageParam>, where ResultType is the contents of a single page, QueryArg is the type passed in as the cache key, and PageParam is the value used to request a specific page.

The endpoint must define an initialPageParam value that will be used as the default (and can be overridden if desired). It also needs a getNextPageParam callback that will calculate the params for each page based on the existing values, and optionally a getPreviousPageParam callback if reverse fetching is needed. Finally, a maxPages option can be provided to limit the entry cache size.

The query and queryFn methods now receive a {queryArg, pageParam} object, instead of just the queryArg.

For the cache entries and hooks, the data field is now an object like {pages: ResultType[], pageParams: PageParam[]>. This gives you flexibility in how you use the data for rendering.

const pokemonApi = createApi({
  baseQuery: fetchBaseQuery({ baseUrl: 'https://example.com/pokemon' }),
  endpoints: (build) => ({
    // 3 TS generics: page contents, query arg, page param
    getInfinitePokemonWithMax: build.infiniteQuery<Pokemon[], string, number>({
      infiniteQueryOptions: {
        // Must provide a default initial page param value
        initialPageParam: 1,
        // Optionally limit the number of cached pages
        maxPages: 3,
        // Must provide a `getNextPageParam` function
        getNextPageParam: (lastPage, allPages, lastPageParam, allPageParams) =>
          lastPageParam + 1,
        // Optionally provide a `getPreviousPageParam` function
        getPreviousPageParam: (
          firstPage,
          allPages,
          firstPageParam,
          allPageParams,
        ) => {
          return firstPageParam > 0 ? firstPageParam - 1 : undefined
        },
      },
      // The `query` function receives `{queryArg, pageParam}` as its argument
</tr></table> 

... (truncated)

Commits

• 18ddd7e Release 2.6.0
• 09e1466 RTKQ Infinite Query integration (#4738)
• 7897c4c Merge pull request #4847 from Tasin5541/doc-lazy-query-reset
• cdb264f doc: update type definitions for lazy query hooks to include reset method
• See full diff in compare view

Updates globals from 15.15.0 to 16.0.0

Release notes

Sourced from globals's releases.

v16.0.0

Breaking

• The serviceworker globals are now generated from browsers (#281) 039ed51
  • It's a breaking change as a few globals have been removed.

---

sindresorhus/globals@v15.15.0...v16.0.0

Commits

• efb3247 16.0.0
• 75cb90a Update globals (#285)
• d018eeb Fix serviceworker environment name (#284)
• f9dd683 Fix filename case
• 039ed51 Add script to get service worker globals (#281)
• See full diff in compare view

Updates prettier from 3.5.1 to 3.5.2

Release notes

Sourced from prettier's releases.

3.5.2

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.5.2

diff

Remove module-sync condition (#17156 by @​fisker)

In Prettier 3.5.0, we added module-sync condition to package.json, so that require("prettier") can use ESM version, but turns out it doesn't work if CommonJS and ESM plugins both imports builtin plugins. To solve this problem, we decide simply remove the module-sync condition, so require("prettier") will still use the CommonJS version, we'll revisit until require(ESM) feature is more stable.

Commits

• 399f427 Release 3.5.2
• bf5aab8 Revert "Use ESM entrypoint for require(ESM)" (#17156)
• c98acab Replace execa with nano-spawn in release script (#17129)
• 4460a4e chore(deps): update eslint related dependencies (#17162)
• f0707f5 chore(deps): update eslint related dependencies (major) (#17163)
• e2624b6 Enforce dependency version be pinned in all packages (#17161)
• 1cee47a chore(deps): update dependency react-markdown to v10 (#17160)
• 7ce2a35 chore(deps): update dependency postcss to v8.5.3 (#17158)
• 1fe7969 chore(deps): update xalvarez/prevent-file-change-action action to v1.9.1 (#17...
• 8eb0630 chore(deps): update dependency knip to v5.44.4 (#17153)
• Additional commits viewable in compare view

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

The following labels could not be found: dependency-bot.