Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.
Detected Package Files
.github/workflows/build.yml (github-actions)
.github/workflows/release.yml (github-actions)
package.json (npm)
Configuration Summary
Based on the default config's presets, Renovate will:
Start dependency updates only once this onboarding PR is merged
Enable Renovate Dependency Dashboard creation
If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
Ignore node_modules, bower_components, vendor and various test/tests directories
Autodetect whether to pin dependencies or maintain ranges
Rate limit PR creation to a maximum of two per hour
Limit to maximum 10 open PRs at any time
Group known monorepo packages together
Use curated list of recommended non-monorepo package groupings
Fix some problems with very old Maven commons versions
Ignore spring cloud 1.x releases
Ignore web3j 5.0.0 release
Ignore http4s digest-based 1.x milestones
Use node versioning for @types/node
Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133
Do not upgrade from Alpine stable to edge
🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.
What to Expect
With your current configuration, Renovate will create 15 Pull Requests:
🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.
❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.
#286789b6dbb3 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.
#2819bbad8c79 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.
#2819bbad8c79 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.
#2759 Thanks @srmagura, @Andarist! - Change the argument of the shouldForwardProp option of styled from PropertyKey to string in the TypeScript definitions.
#23333055efdd Thanks @Andarist! - shouldForwardProp has been changed from being a bivariant method to a contravariant function - it improves the type-safety for those that type this option.
#23333055efdd Thanks @antongolub! - FilteringStyledOptions and StyledOptions types no longer require a type argument for the Props generic.
This is a small CLI to sort any specified json files alphabetically. This was created to sort localization files, but maybe you will find another use case.
4 May 3, 2022
14 Jan 3, 2023
7 May 17, 2022
7 Sep 13, 2022
13 Dec 17, 2022
80 Jan 3, 2023
11 Oct 18, 2022
8 Oct 7, 2022
89 Dec 20, 2022
9 Nov 7, 2022
1 Jan 1, 2022
12 Sep 30, 2022
192 Jan 2, 2023
4 Nov 29, 2022
4 Feb 24, 2022
5 Mar 11, 2022
5 Oct 7, 2022
4 Mar 20, 2022
5 Nov 14, 2022