Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update all non-major dependencies #323

Merged
merged 1 commit into from
May 28, 2023
Merged

Update all non-major dependencies #323

merged 1 commit into from
May 28, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 23, 2022 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@atlaskit/theme 12.1.8 -> 12.5.3 age adoption passing confidence dependencies minor
@babel/helper-builder-react-jsx (source) 7.16.7 -> 7.19.0 age adoption passing confidence dependencies minor
@babel/plugin-proposal-private-property-in-object (source) 7.17.12 -> 7.21.0 age adoption passing confidence dependencies minor
@babel/plugin-transform-classes (source) 7.18.4 -> 7.21.0 age adoption passing confidence devDependencies minor
@emotion/react (source) 11.9.3 -> 11.11.0 age adoption passing confidence dependencies minor
@emotion/styled (source) 11.9.3 -> 11.11.0 age adoption passing confidence dependencies minor
@reduxjs/toolkit (source) 1.8.2 -> 1.9.5 age adoption passing confidence dependencies minor
actions/setup-node v3.3.0 -> v3.6.0 age adoption passing confidence action minor
chrono-node 2.3.8 -> 2.6.3 age adoption passing confidence dependencies minor
react-beautiful-dnd 13.1.0 -> 13.1.1 age adoption passing confidence dependencies patch
react-hook-form (source) 7.32.2 -> 7.44.1 age adoption passing confidence dependencies minor
react-redux 8.0.2 -> 8.0.5 age adoption passing confidence dependencies patch
react-router-dom 5.3.3 -> 5.3.4 age adoption passing confidence dependencies patch
react-virtualized 9.22.3 -> 9.22.5 age adoption passing confidence dependencies patch
react-window (source) 1.8.7 -> 1.8.9 age adoption passing confidence dependencies patch
redux (source) 4.2.0 -> 4.2.1 age adoption passing confidence dependencies patch
styled-components (source) 5.3.5 -> 5.3.11 age adoption passing confidence dependencies patch

Release Notes

babel/babel

v7.19.0

Compare Source

👓 Spec Compliance
🚀 New Feature
  • babel-generator, babel-helpers, babel-parser, babel-plugin-proposal-decorators, babel-plugin-syntax-decorators, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • babel-parser
  • babel-generator, babel-parser
  • babel-standalone
  • babel-helper-create-regexp-features-plugin, babel-helpers, babel-plugin-proposal-duplicate-named-capturing-groups-regex, babel-plugin-transform-named-capturing-groups-regex, babel-standalone
🐛 Bug Fix
  • babel-helper-function-name, babel-helper-wrap-function, babel-plugin-transform-classes
    • #​14897 Fix: class transform should not drop method definition when key contains non-BMP characters (@​JLHwung)
  • babel-plugin-transform-typescript
  • babel-parser
  • babel-helper-builder-react-jsx
💅 Polish
📝 Documentation
🏠 Internal

v7.18.6

Compare Source

👓 Spec Compliance
🐛 Bug Fix
  • babel-helper-remap-async-to-generator, babel-plugin-proposal-async-generator-functions
  • babel-plugin-transform-parameters
  • babel-core
  • babel-core, babel-helper-check-duplicate-nodes, babel-plugin-bugfix-safari-id-destructuring-collision-in-function-expression, babel-plugin-bugfix-v8-spread-parameters-in-optional-chaining, babel-plugin-proposal-destructuring-private, babel-plugin-proposal-optional-chaining, babel-plugin-transform-runtime
🏠 Internal
  • babel-standalone
  • Other
  • babel-generator, babel-types
  • babel-code-frame, babel-core, babel-generator, babel-helper-annotate-as-pure, babel-helper-builder-binary-assignment-operator-visitor, babel-helper-builder-react-jsx, babel-helper-check-duplicate-nodes, babel-helper-compilation-targets, babel-helper-create-class-features-plugin, babel-helper-create-regexp-features-plugin, babel-helper-define-map, babel-helper-explode-assignable-expression, babel-helper-fixtures, babel-helper-function-name, babel-helper-hoist-variables, babel-helper-member-expression-to-functions, babel-helper-module-imports, babel-helper-module-transforms, babel-helper-optimise-call-expression, babel-helper-plugin-test-runner, babel-helper-plugin-utils, babel-helper-remap-async-to-generator, babel-helper-replace-supers, babel-helper-simple-access, babel-helper-split-export-declaration, babel-helper-transform-fixture-test-runner, babel-helper-validator-option, babel-helper-wrap-function, babel-helpers, babel-highlight, babel-plugin-bugfix-v8-spread-parameters-in-optional-chaining, babel-plugin-external-helpers, babel-plugin-proposal-async-generator-functions, babel-plugin-proposal-class-static-block, babel-plugin-proposal-decorators, babel-plugin-proposal-destructuring-private, babel-plugin-proposal-function-bind, babel-plugin-proposal-function-sent, babel-plugin-proposal-json-strings, babel-plugin-proposal-object-rest-spread, babel-plugin-proposal-optional-chaining, babel-plugin-proposal-partial-application, babel-plugin-proposal-pipeline-operator, babel-plugin-proposal-private-property-in-object, babel-plugin-proposal-record-and-tuple, babel-plugin-syntax-typescript, babel-plugin-transform-block-scoped-functions, babel-plugin-transform-block-scoping, babel-plugin-transform-classes, babel-plugin-transform-computed-properties, babel-plugin-transform-destructuring, babel-plugin-transform-duplicate-keys, babel-plugin-transform-exponentiation-operator, babel-plugin-transform-flow-comments, babel-plugin-transform-flow-strip-types, babel-plugin-transform-for-of, babel-plugin-transform-function-name, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-systemjs, babel-plugin-transform-modules-umd, babel-plugin-transform-object-super, babel-plugin-transform-parameters, babel-plugin-transform-property-mutators, babel-plugin-transform-proto-to-assign, babel-plugin-transform-react-constant-elements, babel-plugin-transform-react-display-name, babel-plugin-transform-react-inline-elements, babel-plugin-transform-react-jsx-compat, babel-plugin-transform-react-jsx-source, babel-plugin-transform-react-jsx, babel-plugin-transform-runtime, babel-plugin-transform-typescript, babel-plugin-transform-unicode-escapes, babel-preset-env, babel-preset-typescript, babel-standalone, babel-template, babel-traverse, babel-types
  • babel-core, babel-helper-transform-fixture-test-runner, babel-plugin-transform-destructuring
emotion-js/emotion

v11.11.0

Compare Source

Minor Changes
Patch Changes

v11.10.8

Compare Source

Patch Changes

v11.10.6

Compare Source

Patch Changes

v11.10.5

Compare Source

Patch Changes

v11.10.4

Compare Source

Patch Changes

  • #​2867 89b6dbb3 Thanks @​Andarist! - Externalized code referencing React.useInsertionEffect to a separate @emotion/use-insertion-effect-with-fallbacks package. This package should be used in your defined externals if you bundle Emotion for whatever reason. It references useInsertionEffect in a very specific way that allows us to use it conditionally. However, if the code consuming Emotion is bundled as a library with Emotion in it then some bundlers might change the way in which we reference useInsertionEffect and that might create problems for bundlers used to consume the said library code. By externalizing this new package you can still bundle Emotion if you want to without running into this problem as you won't "destroy" the carefully crafted reference to useInsertionEffect in the process.

    Note that we don't recommend bundling Emotion. You should have very specific reasons to do so.

  • Updated dependencies [89b6dbb3]:

v11.10.0

Compare Source

Minor Changes

  • #​2819 bbad8c79 Thanks @​nicksrandall! - exports field has been added to the package.json manifest. It limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.

  • #​2819 bbad8c79 Thanks @​nicksrandall! - Thanks to the added exports field, the package now includes a worker condition that can be utilized by properly configured bundlers when targeting worker-like environments. It fixes the issue with browser-specific files being prioritized by some bundlers when targeting workers.

Patch Changes
reduxjs/redux-toolkit

v1.9.5

Compare Source

This bugfix release includes notable improvements to TS type inference when using the enhancers option in configureStore, and updates the listener middleware to only check predicates if the dispatched value is truly an action object.

What's Changed

Full Changelog: reduxjs/redux-toolkit@v1.9.4...v1.9.5

v1.9.4

Compare Source

This bugfix release includes tweaks to RTKQ options handling, tweaks for perf updates, dependency updates, and updates to our CI tooling.

Also, please check out our ongoing RTK 2.0 alpha releases! They have significant improvements to bundle size, ESM/CJS compatibility, TS typings, and reducer update performance. We're looking for real-world feedback on behavior, performance, and any issues you might run into.

Changelog

RTK Query Options Updates

Passing transformResponse as part of enhanceEndpoints can now override the TS type of the original data.

fetchBaseQuery now properly checks for a global responseHandler option.

Performance and Internals

RTK Query now uses Immer's original() to do comparisons inside of copyWithStructuralSharing, which should significantly speed up performance when applying changes from re-fetched data.

RTKQ's internal subscriptionUpdated action is now marked as batchable.

We've updated dependencies to Immer 9.0.21, Reselect 4.1.8, and Redux 4.2.1.

CI Updates

We've added a suite of example apps built with different frameworks such as CRA 4, CRA 5, Next, and Vite, as well as examples that check for compatibility in Node with CJS and ESM modes and with various TS module resolution modes.

What's Changed

Full Changelog: reduxjs/redux-toolkit@v1.9.3...v1.9.4

v1.9.3

Compare Source

This release fixes a couple issues with the skip/skipToken options for query hooks, and makes a small perf tweak to serializing query args.

Changelog

Skip Behavior

We made a change in v1.9.0 that tried to make some skip behavior more consistent, including clearing out the cached data. However, we had overlooked that our own docs actually said "skipping a query will keep the cached data", and several users pointed this out as they'd been relying on that behavior.

We've reverted that change. Now, setting {skip: true} or skipToken for a query with existing results will keep the data value (reflecting the last successful query), but currentData will be undefined (reflecting the current settings).

We also identified and fixed an issue that could cause subscription entries to leak under a specific combination of timing and settings changes.

Query Arg Serialization Perf

RTKQ relies on serializing query arguments to serve as the cache keys, with the default using JSON.stringify() + some logic for sorting keys. There was a report that in some apps, large query arg objects could take a while to stringify and this was being done repeatedly. We've added a WeakMap-based cache for query args to avoid re-serializing existing arg values.

What's Changed

Full Changelog: reduxjs/redux-toolkit@v1.9.2...v1.9.3

v1.9.2

Compare Source

This bugfix release fixes a memory leak in createListenerMiddleware, optimizes performance inside serializableMiddleware, adds new options for fetchBaseQuery, adds support for path RegExp exclusions in serializableMiddleware and immutabilityMiddleware, and improves some TS types.

Changelog

Bug Fixes

createListenerMiddleware had a memory leak that turned out to be due to use of Promise.race(). We've restructured the logic to fix that.

fetchBaseQuery now correctly combines global options with endpoint / default options in all cases.

New Options

fetchBaseQuery now supports a jsonReplacer option that will be used when processing JSON.

Both dev check middleware now support regular expressions in the ignoredPaths array in addition to strings. This adds extra flexibility in skipping certain fields.

TS Changes

The CaseReducer type was sometimes incorrectly inferring its return type in rare cases. That's been fixed.

The isAnyOf/isAllOf matcher function TS types have been tweaked to not require an individual first parameter. This allows spreading arrays of matchers as arguments, like const isLoading = isAnyOf(...interestingPendingThunksArray).

Other Changes

The serializableMiddleware now uses a WeakSet if available to cache values it's seen. This should significantly speed up checks against large state values in development builds.

What's Changed

Full Changelog: reduxjs/redux-toolkit@v1.9.1...v1.9.2

v1.9.1

Compare Source

This bugfix release fixes assorted issues that were reported with RTK 1.9.0, and adds a few additional requested tweaks and improvements.

Changelog

Fixes

The createAsyncThunk.withTypes function was fully broken (it type-checked correctly, but pointed to the wrong function due to a name shadowing issue). That now works correctly.

The maxRetries option for RTKQ was inadvertently filtering out 0 values, and those are now accepted.

fulfillWithValue had incorrect types that made it appear as if the data was nested an additional level deeper. The types are now correct.

The ActionCreatorWithoutPayload type was tweaked to force an error when an action creator is accidentally called with an argument, which happens in cases like onClick={todoAdded}. This avoids accidentally passing values like React event objects as the payload.

Timer handling for batchActions and autoBatchEnhancer now works in more JS runtime environments.

Other Changes

The TagDescription type is now exported from RTKQ.

API endpoints now have a .name field containing the endpoint name, such as "getPokemon".

Calling promise.abort() on a createAsyncThunk promise before an async condition resolves will now be treated as if the condition itself returned false, bailing out and not dispatching anything.

The merge option now receives a third argument containing {arg, baseQueryMeta, fulfilledTimeStamp, requestId}, in case that info is useful in deciding how to merge.

The @reduxjs/rtk-codemods package has been updated to fix cases where the createSliceBuilder codemod didn't preserve fields with function variable arguments, like [todoAdded]: adapter.addOne. That package has been updated to v0.0.3.

What's Changed

Full Changelog: reduxjs/redux-toolkit@v1.9.0...v1.9.1

v1.9.0

Compare Source

This feature release adds several new options for RTK Query's createApi and fetchBaseQuery APIs, adds a new upsertQueryData util, rewrites RTKQ's internals for improved performance, adds a new autoBatchEnhancer, deprecates the "object" syntax for createReducer and createSlice.extraReducers, deprecates and removes broken utils for getting running query promises, improves TS inference, exports additional types, and fixes a number of reported issues.

npm i @​reduxjs/toolkit@latest

yarn add @​reduxjs/toolkit@latest

We plan to start work on RTK 2.0 in the next few weeks. RTK 2.0 will focus on dropping legacy build compatibility and deprecated APIs, with some potential new features. See the linked discussion thread and give us feedback on ideas!

Deprecations and Removals

Object Argument for createReducer and createSlice.extraReducers

RTK's createReducer API was originally designed to accept a lookup table of action type strings to case reducers, like { "ADD_TODO" : (state, action) => {} }. We later added the "builder callback" form to allow more flexibility in adding "matchers" and a default handler, and did the same for createSlice.extraReducers.

We intend to remove the "object" form for both createReducer and createSlice.extraReducers in RTK 2.0. The builder callback form is effectively the same number of lines of code, and works much better with TypeScript.

Starting with this release, RTK will print a one-time runtime warning for both createReducer and createSlice.extraReducers if you pass in an object argument.

As an example, this:

const todoAdded = createAction('todos/todoAdded');

createReducer(initialState, {
  [todoAdded]: (state, action) => {}
})

createSlice({
  name,
  initialState,
  reducers: {/* case reducers here */},
  extraReducers: {
    [todoAdded]: (state, action) => {}
  }
})

should be migrated to:

createReducer(initialState, builder => {
  builder.addCase(todoAdded, (state, action) => {})
})

createSlice({
  name,
  initialState,
  reducers: {/* case reducers here */},
  extraReducers: builder => {
    builder.addCase(todoAdded, (state, action) => {})
  }
})
Codemods for Deprecated Object Reducer Syntax

To simplify upgrading codebases, we've published a set of codemods that will automatically transform the deprecated "object" syntax into the equivalent "builder" syntax.

The codemods package is available on NPM as @reduxjs/rtk-codemods. It currently contains two codemods: createReducerBuilder and createSliceBuilder.

To run the codemods against your codebase, run npx @&#8203;reduxjs/rtk-codemods <TRANSFORM NAME> path/of/files/ or/some**/*glob.js.

Examples:

npx @&#8203;reduxjs/rtk-codemods createReducerBuilder ./src

npx @&#8203;reduxjs/rtk-codemods createSliceBuilder ./packages/my-app/**/*.ts

We also recommend re-running Prettier on the codebase before committing the changes.

These codemods should work, but we would greatly appreciate testing and feedback on more real-world codebases!

Object reducer codemod before/after examples Before: 
createReducer(initialState, {
  [todoAdded1a]: (state, action) => {
    // stuff
  },
  [todoAdded1b]: (state, action) => action.payload,
});

const slice1 = createSlice({
  name: "a",
  initialState: {},
  extraReducers: {
    [todoAdded1a]: (state, action) => {
      // stuff
    },
    [todoAdded1b]: (state, action) => action.payload,
  }
})

After:

createReducer(initialState, (builder) => {
  builder.addCase(todoAdded1a, (state, action) => {
    // stuff
  });

  builder.addCase(todoAdded1b, (state, action) => action.payload);
})

const slice1 = createSlice({
  name: "a",
  initialState: {},

  extraReducers: (builder) => {
    builder.addCase(todoAdded1a, (state, action) => {
      // stuff
    });

    builder.addCase(todoAdded1b, (state, action) => action.payload);
  }
})
getRunningOperationPromises Deprecation and Replacement

In v1.7.0, we added an api.util.getRunningOperationPromises() method for use with SSR scenarios, as well as a singular getRunningOperationPromise() method intended for possible use with React Suspense.

Unfortunately, in #​2477 we realized that both those methods have a fatal flaw - they do not work with multiple stores in SSR.

As of this release, we are immediately marking getRunningOperationPromises() as deprecated and discouraging its use before we remove it completely in RTK 2.0! It will now throw both runtime and compile errors in development to enforce moving away from using it. However, we are leaving its existing behavior in production builds to avoid actual breakage.

The getRunningOperationPromise() util was experimental, and as far as we can tell not actually being used by anyone, so we are removing getRunningOperationPromise completely in this release.

As replacements, RTKQ now includes four new thunks attached to api.util:

  • getRunningQueryThunk(endpointName, queryArgs)
  • getRunningMutationThunk(endpointName, fixedCacheKeyOrRequestId)
  • getRunningQueriesThunk()
  • getRunningMutationsThunk()

Usages would typically change like this:

-await Promise.all(api.util.getRunningOperationPromises())
+await Promise.all(dispatch(api.util.getRunningQueriesThunk()))

Changelog

New RTK Query createApi Options

createApi endpoints now have several additional options that can be passed in, some of which are intended to work together.

merge Option

RTKQ was built around the assumption that the server is the source of truth, and every refetch replaces the cached data on the client. There are use cases when it would be useful to merge an incoming response into the existing cached data instead, such as pagination or APIs that return varying results over time.

Query endpoints can now accept a merge(cachedData, responseData) callback that lets you do Immer-powered "mutations" to update the existing cached data instead of replacing it entirely.

Since RTKQ assumes that each response per key should replace the existing cache entry by default, the merge option is expected to be used with the serializeQueryArgs and forceRefetch options, as described below.

serializeQueryArgs Option

RTK Query always serializes the cache key value, and uses the string as the actual key for storing the cache entry. The default serialization is the name of the endpoint, plus either the primitive value or a stable-serialized object. An example might be state.api.queries['getPokemon("pikachu")'].

RTKQ already supported customization of this serialization behavior at the createApi level. Now, each endpoint can specify its own serializeQueryArgs method.

The per-endpoint serializeQueryArgs may return either a string, an object, a number, or a boolean. If it's a string, that value will be used as-is. Otherwise, the return value will be run through the default serialization logic. This simplifies the common case of stripping out a couple unwanted object fields from the cache key.

This option serves two main purposes: leaving out values that are passed in to an endpoint but not really part of the "key" conceptually (like a socket or client instance), and altering cache key behavior to use a single entry for the endpoint (such as in an infinite loading / pagination scenario).

Also, the defaultSerializeQueryArgs util is now exported.

    getPost: build.query<Post, { id: string; client: MyApiClient }>({
      queryFn: async ({ id, client }) => {
        const post = await client.fetchPost(id)
        return { data: post }
      },
      serializeQueryArgs: ({ queryArgs, endpointDefinition, endpointName }) => {
        const { id } = queryArgs
        // This can return a string, an object, a number, or a boolean.
        // If it returns an object, number or boolean, that value
        // will be serialized automatically via `defaultSerializeQueryArgs`
        return { id } // omit `client` from the cache key

        // Alternately, you can use `defaultSerializeQueryArgs`:
        // return defaultSerializeQueryArgs({
        //   endpointName,
        //   queryArgs: { id },
        //   endpointDefinition
        // })
        // Or  create and return a string yourself:
        // return `getPost(${id})`
      },
    }),
forceRefresh option

Sometimes you may want to force a refetch, even though RTKQ thinks that the serialized query args haven't changed and there's already a fulfilled cache entry.

This can be used to force RTKQ to actually refetch. One expected use case is an "infinite pagination" scenario where there is one cache entry for the endpoint, different page numbers are given as query args, and the incoming responses are merged into the existing cache entry:

    listItems: build.query<string[], number>({
      query: (pageNumber) => `/listItems?page=${pageNumber}`,
      // Only have one cache entry because the arg always maps to one string
      serializeQueryArgs: ({ endpointName }) => {
        return endpointName
      },
      // Always merge incoming data to the cache entry
      merge: (currentCache, newItems) => {
        currentCache.push(...newItems)
      },
      // Refetch when the page arg changes
      forceRefetch({ currentArg, previousArg }) {
        return currentArg !== previousArg
      },
    }),
transformErrorResponse Option

Similar to transformResponse, endpoints can now specify a transformErrorResponse option as well.

upsertQueryData Util

RTKQ already has an updateQueryData util to synchronously modify the contents of an existing cache entry, but there was no way to create a new cache entry and its metadata programmatically.

This release adds a new api.util.upsertQueryData API that allows creating a cache entry + its data programmatically. As with the other util methods, this is a thunk that should be dispatched, and you should pass in the exact cache key arg and complete data value you want to insert:

dispatch(
  api.util.upsertQueryData('post', '3', {
    id: '3',
    title: 'All about cheese.',
    contents: 'I love cheese!',
   })
)

The dispatch acts like all other RTKQ requests, so the process is async, and the thunk returns a promise that resolves when the upsert is complete.

RTK Query Performance Improvements

We've significa

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 Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Jun 23, 2022 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
eventmanny ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 28, 2023 9:30pm

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from be02bbc to 25e4238 Compare June 24, 2022 11:28
@renovate renovate bot changed the title Update dependency @atlaskit/theme to v12.1.9 Update all non-major dependencies Jun 24, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 25e4238 to a1bbe41 Compare June 27, 2022 20:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a1bbe41 to 175bddc Compare June 30, 2022 05:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 175bddc to 0d432fa Compare July 1, 2022 11:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0d432fa to 0e15a12 Compare July 3, 2022 04:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0e15a12 to 472fc3e Compare July 8, 2022 12:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 472fc3e to 1318b1b Compare July 9, 2022 18:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1318b1b to ad5e6d8 Compare July 11, 2022 16:09
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ad5e6d8 to a86baa9 Compare July 14, 2022 12:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a86baa9 to 94cf230 Compare July 18, 2022 10:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 94cf230 to c2e8208 Compare July 29, 2022 00:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c2e8208 to 5c7e23c Compare July 31, 2022 09:34
@renovate renovate bot changed the title Update all non-major dependencies Update all non-major dependencies to v12.1.9 Aug 9, 2022
@renovate renovate bot changed the title Update all non-major dependencies to v12.1.9 Update all non-major dependencies Aug 10, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5c7e23c to f219035 Compare August 11, 2022 02:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f871c65 to 03691c6 Compare August 19, 2022 23:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f470ace to f77a331 Compare March 16, 2023 17:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f77a331 to d647fe1 Compare March 23, 2023 19:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d647fe1 to 7ea2d25 Compare March 25, 2023 01:27
@socket-security
Copy link

socket-security bot commented Mar 25, 2023 •
edited
Loading

New dependency changes detected. Learn more about Socket for GitHub ↗︎

👍 No new dependency issues detected in pull request

Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

⚠️ Please accept the latest app permissions to ensure bot commands work properly. Accept the new permissions here.

Pull request alert summary
Issue Status
Install scripts ✅ 0 issues
Native code ✅ 0 issues
Bin script shell injection ✅ 0 issues
Unresolved require ✅ 0 issues
Invalid package.json ✅ 0 issues
HTTP dependency ✅ 0 issues
Git dependency ✅ 0 issues
Potential typo squat ✅ 0 issues
Known Malware ✅ 0 issues
Telemetry ✅ 0 issues
Protestware/Troll package ✅ 0 issues

📊 Modified Dependency Overview:

⬆️ Updated Package Version Diff Added Capability Access +/- Transitive Count Publisher
@reduxjs/toolkit@1.9.5 1.8.2...1.9.5 None +5/-5 acemarke
react-redux@8.0.5 8.0.2...8.0.5 None +1/-1 acemarke
redux@4.2.1 4.2.0...4.2.1 None +0/-0 acemarke
react-beautiful-dnd@13.1.1 13.1.0...13.1.1 None +1/-1 delcore92
react-window@1.8.9 1.8.7...1.8.9 None +0/-0 brianvaughn
@emotion/react@11.11.0 11.9.3...11.11.0 None +15/-37 emotion-release-bot
@emotion/styled@11.11.0 11.9.3...11.11.0 None +17/-39 emotion-release-bot
styled-components@5.3.11 5.3.5...5.3.11 None +13/-19 probablyup
@babel/plugin-proposal-private-property-in-object@7.21.0 7.17.12...7.21.0 None +24/-28 nicolo-ribaudo
@babel/helper-builder-react-jsx@7.19.0 7.16.7...7.19.0 None +0/-3 nicolo-ribaudo
react-virtualized@9.22.5 9.22.3...9.22.5 None +0/-2 brianvaughn
@babel/plugin-transform-classes@7.21.0 7.18.4...7.21.0 None +22/-30 nicolo-ribaudo
chrono-node@2.6.3 2.3.8...2.6.3 None +0/-0 wanasit
react-router-dom@5.3.4 5.3.3...5.3.4 None +1/-2 mjackson
react-hook-form@7.44.1 7.32.2...7.44.1 network +0/-0 bluebill1049
@atlaskit/theme@12.5.3 12.1.8...12.5.3 None +16/-19 atlaskit

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7ea2d25 to 19579a8 Compare March 26, 2023 17:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 19579a8 to d00d427 Compare March 28, 2023 02:17
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d00d427 to 30dce2a Compare March 30, 2023 22:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 30dce2a to d3ec178 Compare April 17, 2023 12:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d3ec178 to acd5f42 Compare April 17, 2023 20:24
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from acd5f42 to d32fad3 Compare April 18, 2023 03:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d32fad3 to eb6f239 Compare May 28, 2023 10:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from eb6f239 to 44c86ed Compare May 28, 2023 21:24
@flicken flicken merged commit 18bf83e into master May 28, 2023
@flicken flicken deleted the renovate/all-minor-patch branch May 28, 2023 21:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@flicken