search

Utdanningsdirektoratet / Grep-komponenter

Komponentbibliotek for Grep. Brukes i Læreplanutvikleren og Grepadmin
2 stars 0 forks source link

chore(deps-dev): bump the major-dependecies group with 6 updates #2964

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 8 months ago

Bumps the major-dependecies group with 6 updates:

Package From To
@typescript-eslint/eslint-plugin 6.19.0 7.0.1
@typescript-eslint/parser 6.19.0 7.0.1
husky 8.0.3 9.0.10
react-router 5.3.4 6.22.0
react-router-dom 5.3.4 6.22.0
semantic-release 22.0.12 23.0.2

Updates @typescript-eslint/eslint-plugin from 6.19.0 to 7.0.1

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v7.0.1

7.0.1 (2024-02-12)

🩹 Fixes

  • eslint-plugin: update peer dep for parser (#8441)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

v7.0.0

7.0.0 (2024-02-12)

Read more about this release: https://typescript-eslint.io/blog/announcing-typescript-eslint-v7/

🚀 Features

  • add support for flat configs (#7935)

🩹 Fixes

  • eslint-plugin: [prefer-find] stop throwing type errors when converting symbols to numbers (#8390)

⚠️ Breaking Changes

  • ⚠️ bump ESLint, NodeJS, and TS minimum version requirements (#8377)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

v6.21.0

6.21.0 (2024-02-05)

... (truncated)

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

7.0.1 (2024-02-12)

🩹 Fixes

  • eslint-plugin: update peer dep for parser

❤️ Thank You

  • Tim Dorr

You can read about our versioning strategy and releases on our website.

7.0.0 (2024-02-12)

🚀 Features

  • ⚠️ bump ESLint, NodeJS, and TS minimum version requirements

  • add support for flat configs

🩹 Fixes

  • eslint-plugin: [prefer-find] stop throwing type errors when converting symbols to numbers

⚠️ Breaking Changes

  • ⚠️ bump ESLint, NodeJS, and TS minimum version requirements

❤️ Thank You

  • Brad Zacher
  • Kirk Waiblinger
  • StyleShit
  • YeonJuan

You can read about our versioning strategy and releases on our website.

6.21.0 (2024-02-05)

🚀 Features

  • export plugin metadata

  • allow parserOptions.project: false

... (truncated)

Commits
  • 4f3215f chore(release): publish 7.0.1
  • 422791c fix(eslint-plugin): update peer dep for parser (#8441)
  • b27de99 chore(release): publish 7.0.0
  • 379f742 chore(eslint-plugin): [no-confusing-void-expression] explicitly state default...
  • b636baa docs: fix restrict-plus-operands example (#8362)
  • 1aa393c chore(deps): update dependency prettier to v3.2.5 (#8401)
  • 8ef5f4b feat: add support for flat configs (#7935)
  • c298350 fix(eslint-plugin): [prefer-find] stop throwing type errors when converting s...
  • 1200b4c chore(deps): update nx to v17.3.0 (#8317)
  • 584db29 feat: bump ESLint, NodeJS, and TS minimum version requirements (#8377)
  • Additional commits viewable in compare view


Updates @typescript-eslint/parser from 6.19.0 to 7.0.1

Release notes

Sourced from @​typescript-eslint/parser's releases.

v7.0.1

7.0.1 (2024-02-12)

🩹 Fixes

  • eslint-plugin: update peer dep for parser (#8441)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

v7.0.0

7.0.0 (2024-02-12)

Read more about this release: https://typescript-eslint.io/blog/announcing-typescript-eslint-v7/

🚀 Features

  • add support for flat configs (#7935)

🩹 Fixes

  • eslint-plugin: [prefer-find] stop throwing type errors when converting symbols to numbers (#8390)

⚠️ Breaking Changes

  • ⚠️ bump ESLint, NodeJS, and TS minimum version requirements (#8377)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

v6.21.0

6.21.0 (2024-02-05)

... (truncated)

Changelog

Sourced from @​typescript-eslint/parser's changelog.

7.0.1 (2024-02-12)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.0.0 (2024-02-12)

🚀 Features

  • ⚠️ bump ESLint, NodeJS, and TS minimum version requirements

  • add support for flat configs

⚠️ Breaking Changes

  • ⚠️ bump ESLint, NodeJS, and TS minimum version requirements

❤️ Thank You

  • Brad Zacher
  • Kirk Waiblinger
  • StyleShit
  • YeonJuan

You can read about our versioning strategy and releases on our website.

6.21.0 (2024-02-05)

🚀 Features

  • allow parserOptions.project: false

❤️ Thank You

  • auvred
  • Brad Zacher
  • Kirk Waiblinger
  • Pete Gonzalez
  • YeonJuan

You can read about our versioning strategy and releases on our website.

6.20.0 (2024-01-29)

This was a version bump only for parser to align it with other projects, there were no code changes.

... (truncated)

Commits
  • 4f3215f chore(release): publish 7.0.1
  • b27de99 chore(release): publish 7.0.0
  • 1aa393c chore(deps): update dependency prettier to v3.2.5 (#8401)
  • 8ef5f4b feat: add support for flat configs (#7935)
  • 1200b4c chore(deps): update nx to v17.3.0 (#8317)
  • 584db29 feat: bump ESLint, NodeJS, and TS minimum version requirements (#8377)
  • 289ee88 chore(release): publish 6.21.0
  • aa5edf7 chore(deps): update dependency prettier to v3.2.4 (#8357)
  • 45c0cb2 chore: cleanup test-utils naming/locations (#8341)
  • a01a6e6 chore(release): publish 6.20.0
  • Additional commits viewable in compare view


Updates husky from 8.0.3 to 9.0.10

Release notes

Sourced from husky's releases.

v9.0.10

v9.0.9

v9.0.8

v9.0.7

v9.0.6

v9.0.5

v9.0.4

v9.0.3

v9.0.2

v9.0.1

... (truncated)

Commits


Updates react-router from 5.3.4 to 6.22.0

Release notes

Sourced from react-router's releases.

v6.22.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6220

v6.21.3

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6213

v6.21.2

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6212

v6.21.1

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6211

v6.21.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6210

v6.20.1

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6201

v6.20.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6200

v6.19.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6190

v6.18.0

Minor Changes

New Fetcher APIs

Per this RFC, we've introduced some new APIs that give you more granular control over your fetcher behaviors. (#10960)

  • You may now specify your own fetcher identifier via useFetcher({ key: string }), which allows you to access the same fetcher instance from different components in your application without prop-drilling
  • Fetcher keys are now exposed on the fetchers returned from useFetchers so that they can be looked up by key
  • Form and useSumbit now support optional navigate/fetcherKey props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified key
    • <Form method="post" navigate={false} fetcherKey="my-key">
    • submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })
    • Invoking a fetcher in this way is ephemeral and stateless
    • If you need to access the state of one of these fetchers, you will need to leverage useFetchers() or useFetcher({ key }) to look it up elsewhere

Persistence Future Flag (future.v7_fetcherPersist)

Per the same RFC as above, we've introduced a new future.v7_fetcherPersist flag that allows you to opt-into the new fetcher persistence/cleanup behavior. Instead of being immediately cleaned up on unmount, fetchers will persist until they return to an idle state. This makes pending/optimistic UI much easier in scenarios where the originating fetcher needs to unmount. (#10962)

  • This is sort of a long-standing bug fix as the useFetchers() API was always supposed to only reflect in-flight fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to an idle state
  • Keep an eye out for the following specific behavioral changes when opting into this flag and check your app for compatibility:
    • Fetchers that complete while still mounted will no longer appear in useFetchers() after completion - they served no purpose in there since you can access the data via useFetcher().data
    • Fetchers that previously unmounted while in-flight will not be immediately aborted and will instead be cleaned up once they return to an idle state
      • They will remain exposed via useFetchers while in-flight so you can still access pending/optimistic data after unmount
      • If a fetcher is no longer mounted when it completes, then it's result will not be post processed - e.g., redirects will not be followed and errors will not bubble up in the UI
      • However, if a fetcher was re-mounted elsewhere in the tree using the same key, then it's result will be processed, even if the originating fetcher was unmounted

... (truncated)

Changelog

Sourced from react-router's changelog.

6.22.0

Patch Changes

  • Updated dependencies:
    • @remix-run/router@1.15.0

6.21.3

Patch Changes

  • Remove leftover unstable_ prefix from Blocker/BlockerFunction types (#11187)

6.21.2

Patch Changes

  • Updated dependencies:
    • @remix-run/router@1.14.2

6.21.1

Patch Changes

  • Fix bug with route.lazy not working correctly on initial SPA load when v7_partialHydration is specified (#11121)
  • Updated dependencies:
    • @remix-run/router@1.14.1

6.21.0

Minor Changes

  • Add a new future.v7_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. (#11087)

    This fix was originally added in #10983 and was later reverted in #11078 because it was determined that a large number of existing applications were relying on the buggy behavior (see #11052)

    The Bug The buggy behavior is that without this flag, the default behavior when resolving relative paths is to ignore any splat (*) portion of the current route path.

    The Background This decision was originally made thinking that it would make the concept of nested different sections of your apps in <Routes> easier if relative routing would replace the current splat:

    <BrowserRouter>
  <Routes>
    <Route path="/" element={<Home />} />
    <Route path="dashboard/*" element={<Dashboard />} />
  </Routes>
</BrowserRouter>

... (truncated)

Commits


Updates react-router-dom from 5.3.4 to 6.22.0

Release notes

Sourced from react-router-dom's releases.

v6.4.4

What's Changed

  • Throw an error if an action/loader function returns undefined as revalidations need to know whether the loader has previously been executed. undefined also causes issues during SSR stringification for hydration. You should always ensure your loader/action returns a value, and you may return null if you don't wish to return anything. (#9511)
  • Properly handle redirects to external domains (#9590, #9654)
  • Preserve the HTTP method on 307/308 redirects (#9597)
  • Support basename in static data routers (#9591)
  • Enhanced ErrorResponse bodies to contain more descriptive text in internal 403/404/405 scenarios
  • Fix issues with encoded characters in NavLink and descendant <Routes> (#9589, #9647)
  • Properly serialize/deserialize ErrorResponse instances when using built-in hydration (#9593)
  • Support basename in static data routers (#9591)
  • Updated dependencies:
    • @remix-run/router@1.0.4
    • react-router@6.4.4

Full Changelog: https://github.com/remix-run/react-router/compare/react-router-dom@6.4.3...react-router-dom@6.4.4

react-router-dom@6.4.0-pre.15

Patch Changes

  • fix: remove internal router singleton (#9227)

    This change removes the internal module-level routerSingleton we create and maintain inside our data routers since it was causing a number of headaches for non-simple use cases:

    • Unit tests are a pain because you need to find a way to reset the singleton in-between tests
      • Use use a _resetModuleScope singleton for our tests
      • ...but this isn't exposed to users who may want to do their own tests around our router
    • The JSX children <Route> objects cause non-intuitive behavior based on idiomatic react expectations
      • Conditional runtime <Route>'s won't get picked up
      • Adding new <Route>'s during local dev won't get picked up during HMR
      • Using external state in your elements doesn't work as one might expect (see #9225)

    Instead, we are going to lift the singleton out into user-land, so that they create the router singleton and manage it outside the react tree - which is what react 18 is encouraging with useSyncExternalStore anyways! This also means that since users create the router - there's no longer any difference in the rendering aspect for memory/browser/hash routers (which only impacts router/history creation) - so we can get rid of those and trim to a simple RouterProvider

    // Before
function App() {
  <DataBrowserRouter>
    <Route path="/" element={<Layout />}>
      <Route index element={<Home />}>
    </Route>
  <DataBrowserRouter>
}

    // After
let router = createBrowserRouter([{
path: "/",
element: <Layout />,
children: [{
index: true,

... (truncated)

Changelog

Sourced from react-router-dom's changelog.

6.22.0

Minor Changes

  • Include a window__reactRouterVersion tag for CWV Report detection (#11222)

Patch Changes

  • Updated dependencies:
    • @remix-run/router@1.15.0
    • react-router@6.22.0

6.21.3

Patch Changes

  • Fix NavLink isPending when a basename is used (#11195)
  • Remove leftover unstable_ prefix from Blocker/BlockerFunction types (#11187)
  • Updated dependencies:
    • react-router@6.21.3

6.21.2

Patch Changes

  • Leverage useId for internal fetcher keys when available (#11166)
  • Updated dependencies:
    • @remix-run/router@1.14.2
    • react-router@6.21.2

6.21.1

Patch Changes

  • Updated dependencies:
    • react-router@6.21.1
    • @remix-run/router@1.14.1

6.21.0

Minor Changes

  • Add a new future.v7_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. (#11087)

    This fix was originally added in #10983 and was later reverted in #11078 because it was determined that a large number of existing applications were relying on the buggy behavior (see #11052)

    The Bug The buggy behavior is that without this flag, the default behavior when resolving relative paths is to ignore any splat (*) portion of the current route path.

    The Background

... (truncated)

Commits


Updates semantic-release from 22.0.12 to 23.0.2

Release notes

Sourced from semantic-release's releases.

v23.0.2

23.0.2 (2024-02-07)

Bug Fixes

v23.0.1

23.0.1 (2024-02-06)

Bug Fixes

  • deps: update dependency marked-terminal to v7 (9faded8)

v23.0.0

23.0.0 (2024-01-12)

Bug Fixes

  • deps: update dependency cosmiconfig to v9 (#3105) (07dde04)
  • deps: update dependency marked to v11 (#3079) (6d2a6f1)
  • deps: upgraded to the latest version of env-ci (0d0ed9d)
  • use one note reference per tag to prevent conflicts (#2085) (020ea7d)

Features

BREAKING CHANGES

related to https://github.com/semantic-release/semantic-release/discussions/3088

v23.0.0-beta.5

23.0.0-beta.5 (2024-01-05)

Bug Fixes

... (truncated)

Commits
  • 38105f5 fix(deps): update dependency marked to v12 (#3176)
  • 7fb784f ci(action): update actions/upload-artifact action to v4.3.1 (#3181)
  • e3245f3 ci(action): update actions/setup-node action to v4.0.2 (#3184)
  • 28bcc1d chore(deps): update dependency prettier to v3.2.5 (#3177)
  • 9faded8 fix(deps): update dependency marked-terminal to v7
  • fccab39 chore(deps): lock file maintenance (#3179)
  • 6be2280 chore(deps): update dependency got to v14.2.0 (#3175)
  • 518b47d chore(deps): update dependency npm-run-all2 to v6.1.2 (#3171)
  • c6c01aa ci(action): update github/codeql-action action to v3.24.0 (#3173)
  • ee4f99f chore(deps): update dependency ava to v6.1.1 (#3168)
  • Additional commits viewable in compare view


Most Recent Ignore Conditions Applied to This Pull Request | Dependency Name | Ignore Conditions | | --- | --- | | react-router | [< 6.1, > 6.0.2] | | react-router-dom | [< 6.1, > 6.0.2] |

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 8 months ago

Superseded by #2965.