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

chore(deps): update all (major) #478

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): update all (major) #478

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 20, 2023 •
edited
Loading

Mend Renovate logo banner

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
actions/checkout action major v2 -> v4 age adoption passing confidence
actions/checkout action major v3 -> v4 age adoption passing confidence
actions/download-artifact action major v1 -> v3 age adoption passing confidence
actions/setup-node action major v3 -> v4 age adoption passing confidence
express-winston dependencies major 3.4.0 -> 4.2.0 age adoption passing confidence
history dependencies major 4.10.1 -> 5.3.0 age adoption passing confidence
http-proxy-middleware dependencies major 0.21.0 -> 2.0.6 age adoption passing confidence
styled-components (source) devDependencies major 4.4.1 -> 6.1.1 age adoption passing confidence

Release Notes

actions/checkout (actions/checkout)

v4

Compare Source

v3

Compare Source

actions/download-artifact (actions/download-artifact)

v3

Compare Source

v2

Compare Source

actions/setup-node (actions/setup-node)

v4

Compare Source

bithavoc/express-winston (express-winston)

v4.2.0

Compare Source

  • Upgraded lodash to 4.17.21 minimum (#​264)
  • Fixed typos and Readme format (#​262)

v4.1.0

Compare Source

  • Update chalk and lodash due minor security impact (#​252)
  • Allow filter out whitelisted request body (#​258)
  • Fix metaField/requestField/responseField typescript types (#​259)

v4.0.5

Compare Source

  • Fix excess semicolon breaking Typescript compilation (#​249)

v4.0.4

Compare Source

  • Update lodash to 4.17.19 (#​245)
  • Update statusLevels to accept Boolean or StatusLevel object in TypeScript definition (#​244)

v4.0.3

Compare Source

  • Update lodash to 4.17.15 (#​232)
  • Add missing exceptionToMeta and skip to TypeScript definition (#​234)

v4.0.2

Compare Source

  • Add blacklist fields to BaseErrorLoggerOptions interface (#​230)

v4.0.1

Compare Source

  • Added headerBlacklist to BaseLoggerOptions for better typescript support (#​228)

v4.0.0

Compare Source

  • Changed metaField configuration property functionality (see Readme.md) (#​209) - BREAKING CHANGE
  • Moved type definitions to be embedded inside library (#​123)
  • Added "files" to package.json to reduce unnecessary files in released package
  • Added StackDriver/Google Cloud Logging specific instructions to Readme.md
  • Added requestField and responseField options to allow storing the request and response in different metadata fields (or not at all)
  • Fixed meta configuration option on errorLogger (was not functioning at all)
  • Added .editorconfig and reformatted library to match
remix-run/history (history)

v5.3.0

Compare Source

This release provides support for native ESM consumption of all exports.

v5.2.0

Compare Source

🐛 Bug fixes

  • Fixed a few type declarations and deprecated the following types:
    • State (now set to unknown which will require consumer type narrowing)
    • PartialPath (use Partial<Path> instead)
    • PartialLocation (use Partial<Location> instead)
  • Fixed a regression related to the createPath return value (#​813)

✨ Features

  • We now use statically analyzable CJS exports. This enables named imports in Node ESM scripts (See the commit).

Full Changelog: remix-run/history@v5.1.0...v5.2.0

v5.1.0

Compare Source

Because the prior 5.0.2 release removed the State type parameter from Location, this was technically a breaking change. To correct for this, I'm bumping this as a minor release. It won't affect runtime code, but it may affect your development experience and tests if you were using that parameter.

The State type export is also restored, so you shouldn't have issues with installing React Router v6.

Oh, by the way, did you hear we released React Router v6?

Full Changelog: remix-run/history@v5.0.3...v5.1.0

v5.0.3

Compare Source

Fixed parsePath adding incorrectly adding search

v5.0.2

Compare Source

Just a couple fixes:

  • Fixed search params persisting on redirects
  • Changed the location.state type to any and removed the generic on Location

Full Changelog: remix-run/history@v5.0.1...v5.0.2

v5.0.1

Compare Source

This patch release contains a tiny TypeScript update to use the built-in Partial utility for PartialPath and PartialLocation. We always love it when we can ship just a little less code!

🙏 Credits

Thanks to @​liuhanqu, @​hanquliu, @​chaance and @​mjackson for your contributions!

v5.0.0

Compare Source

Today we are very pleased to announce the stable release of history version 5!

Overview

This version includes many enhancements and fixes a few important issues with the library.

New Features
  • Hash history now has support for location.state
  • Better history.block API, with support for retrying transitions
  • Full TypeScript declarations and IntelliSense docs
  • Adds development and production builds for <script type=module> users
  • Both browser and hash history have support for iframes (custom window objects)
  • About 50% smaller than v4 (and no dependencies)
Bugfixes
  • Fixed some long-standing encoding issues with location.pathname
  • Removed unfixable warnings about pushing the same path in hash history
  • Renamed browser global to HistoryLibrary so it doesn't conflict with window.History
Breaking Changes
  • Removed support for browsers that do not support the HTML5 history API (no pushState)
  • Removed relative pathname support in hash history and memory history
  • Removed getUserConfirmation, keyLength, and hashType APIs

Usage

Please refer to our installation guide for instructions about how to install the library.

There is also a getting started guide as well as a complete API reference in the docs folder.

We are very excited about this release, especially because it will serve as the foundation for the upcoming release of React Router version 6.

Thank you for your support. Enjoy! 😀

chimurai/http-proxy-middleware (http-proxy-middleware)

v2.0.6

Compare Source

  • fix(proxyReqWs): catch socket errors (#​763)

v2.0.5

Compare Source

  • fix(error handler): add default handler to econnreset (#​759)

v2.0.4

Compare Source

  • fix(fix-request-body): improve content type check (#​725) (kevinxh)

v2.0.3

Compare Source

v2.0.2

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source

  • chore(package): drop node 10 [BREAKING CHANGE] (#​577)

v1.3.1

Compare Source

  • fix(fix-request-body): make sure the content-type exists (#​578) (oufeng)

v1.3.0

Compare Source

  • docs(response interceptor): align with nodejs default utf8 (#​567)
  • feat: try to proxy body even after body-parser middleware (#​492) (midgleyc)

v1.2.1

Compare Source

  • fix(response interceptor): proxy original response headers (#​563)

v1.2.0

Compare Source

  • feat(handler): response interceptor (#​520)
  • fix(log error): handle undefined target when websocket errors (#​527)

v1.1.2

Compare Source

  • fix(log error): handle optional target (#​523)

v1.1.1

Compare Source

  • fix(error handler): re-throw http-proxy missing target error (#​517)
  • refactor(dependency): remove camelcase
  • fix(option): optional target when router is used (#​512)

v1.1.0

Compare Source

v1.0.6

Compare Source

  • chore(deps): lodash 4.17.20 (#​475)

v1.0.5

Compare Source

  • chore(deps): lodash 4.17.19 (#​454)

v1.0.4

Compare Source

  • chore(deps): http-proxy 1.18.1 (#​442)

v1.0.3

Compare Source

  • build(package): exclude build artifact tsconfig.tsbuildinfo (#​415)

v1.0.2

Compare Source

  • fix(router): handle rejected promise in custom router (#​410) (bforbis)

v1.0.1

Compare Source

  • fix(typescript): fix proxyRes and router types (#​410) (dylang)

v1.0.0

Compare Source

  • feat(createProxyMiddleware): explicit import http-proxy-middleware (BREAKING CHANGE)(#​400)
  • feat(typescript): export http-proxy-middleware types (#​400)
  • fix(typescript): ES6 target - TS1192 (#​400)
styled-components/styled-components (styled-components)

v6.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.1.0...v6.1.1

v6.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.9...v6.1.0

v6.0.9

Compare Source

fix bundling to not hardcode window (should fix some testing use cases that were incorrectly assuming a server environment when JSDOM and similar are in use)

Full Changelog: styled-components/styled-components@v6.0.8...v6.0.9

v6.0.8

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.7...v6.0.8

v6.0.7

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.6...v6.0.7

v6.0.6

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.5...v6.0.6

v6.0.5

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.4...v6.0.5

v6.0.4

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.3...v6.0.4

v6.0.3

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.2...v6.0.3

v6.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.1...v6.0.2

v6.0.1

Compare Source

Fixed an issue where a dev-time warning was being triggered too eagerly.

Full Changelog: styled-components/styled-components@v6.0.0...v6.0.1

v6.0.0

Compare Source

yarn add styled-components

Changed in this version

  • fix(types): prevent prop bleed on styling properties (fixes #​4053, c0f8015)
  • feat(types): ship csstype via "CSS" namespace (e6c4f0a)
  • chore: bump stylis to 4.3 (fixes #​4007, fa58875)
  • reduced some sources of unnecessary branching logic

Breaking changes in v6

Migration guide → https://styled-components.com/docs/faqs#what-do-i-need-to-do-to-migrate-to-v6

  • now using stylis v4 (if using stylis-plugin-rtl you'll need to upgrade to the newer version)
  • styled-components now provides its own types; if you installed @types/styled-components in the past, you'll want to remove it
  • dropped $as and $forwardedAs props (use as or forwardedAs)
  • dropped automatic prop filtering; use transient props ($ prefix) for stuff you don't want to be passed to child component / HTML
  • StyleSheetManager
    • replaced disableVendorPrefixes with enableVendorPrefixes prop
    • dropped automatic vendor prefixing; if you need to support older browsers, you can re-enable it easily with the above prop 
      <StyleSheetManager enableVendorPrefixes>
  {/* your React tree and ThemeProvider goes here */}
</StyleSheetManager>
  • dropped deprecated withComponent API (87f511a); use "as" prop instead
  • node >= 14 needed

Full Changelog: styled-components/styled-components@v5.3.7...v6.0.0

v5.3.11

Compare Source

Removed use of the useDebugValue hook to rectify older React support.

Full Changelog: styled-components/styled-components@v5.3.10...v5.3.11

v5.3.10

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v5.3.9...v5.3.10

v5.3.9

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v5.3.8...v5.3.9

v5.3.8

Compare Source

What's Changed

fix(constants): rework process env guard

Full Changelog: styled-components/styled-components@v5.3.7-fixed...v5.3.8

v5.3.7

Compare Source

v5.3.6

Compare Source

What's Changed

Deprecations

  • $as and $forwardedAs will be removed in the next major version, use the unprefixed props instead

New Contributors

Full Changelog: styled-components/styled-components@v5.3.5...v5.3.6

v5.3.5

Add statement of solidarity against the war on Ukraine 🇺🇦

v5.3.3

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v5.3.1...v5.3.3

v5.3.1

Compare Source

v5.3.0

Compare Source

  • Pass elementToBeCreated as a third parameter to shouldForwardProp so that the user-specified function can decide whether to pass through props based on whether the created element will be a tag or another component. (see #​3436)

  • Fix React Native components accepts function as style prop. (see #​3389)

v5.2.3

Compare Source

fix an issue with an unguarded window accessor in a SSR path (see #​3446)

v5.2.2

Compare Source

  • For React Native based components, pass testID down to the native component if specified for an easier time testing. (see #​3365)

  • Enable users of the babel macro to customize the styled-components import with importModuleName (see #​3422)

  • [fix] COMPLEX_SELECTOR_PREFIX.includes wasn't transpiled (see #​3397)

v5.2.1

Compare Source

Tweak server-side build settings to resolve an issue with jest-dom not being able to pick up generated styles (see #​3308) thanks @​Lazyuki

v5.2.0

Compare Source

  • Make sure StyleSheetManager renders all styles in iframe / child windows (see #​3159) thanks @​eramdam!

  • Rework how components self-reference in extension scenarios (see #​3236); should fix a bunch of subtle bugs around patterns like & + &

  • Fix keyframes not receiving a modified stylis instance when using something like stylis-plugin-rtl (see #​3239)

  • Big performance gain for components using style objects (see #​3239)

  • We no longer emit dynamic classNames for empty rulesets, so some className churn may occur in snapshots

  • Preallocate global style placement to ensure cGS is consistently inserted at the top of the stylesheet; note that this is done in runtime order so, if you have multiple cGS that have overlapping styles, ensure they're defined in code in the sequence you would want them injected (see #​3239)

  • Add "engines" to package.json (currently set to Node 10, the oldest supported LTS distribution) (see #​3201) thanks @​MichaelDeBoey!

Finally, special thanks to @​willheslam for testing and some last minute fixes on this release!

v5.1.1

Compare Source

New Functionality
  • Implement shouldForwardProp API for native and primitive platforms, which was previously missing in [v5.1.0] (see #​3093)
    This has been released under a patch bump instead of a minor, since it's only been missing from Native-support.
Bugfixes
  • Added useTheme hook to named exports for react-primitives entrypoint (see #​2982) thanks @​jladuval!
  • Escape every CSS ident character necessary when converting component display names to class names (see #​3102) thanks @​kripod!

v5.1.0

Compare Source

New Functionality

  • Add shouldForwardProp API (almost the same as emotion's, just a slightly different usage pattern); https://github.com/styled-components/styled-components/pull/3006

    Sometimes when composing multiple higher-order components together, it's possible to get into scenarios when multiple layers consume props by the same name. In the past we've introduced various workarounds for popular props like "as" but this power-user API allows for more granular customization of what props are passed down to descendant component children when using the styled() HOC wrapper.

    When combined with other APIs like .attrs() this becomes a very powerful constellation of abilities.

    Here's how you use it:

    const Comp = styled('div').withConfig({
  shouldForwardProp: (prop, defaultValidatorFn) => !['filterThis'].includes(prop),
})`
  color: red;
`;

render(<Comp filterThis="abc" passThru="def" />);

Renders: 


The second argument `defaultValidatorFn` is what we use internally to validate props based on known HTML attributes. It's provided so you can filter exactly what props you don't wish to pass and then fall-back to the default filtering mechanism if desired.

Other methods on the `styled` HOC like `.attrs` can be chained after `withConfig()`, and before opening your template literal:

```jsx
const Comp = styled('div').withConfig({
  shouldForwardProp: (prop, defaultValidatorFn) => !['filterThis'].includes(prop),
}).attrs({ className: 'foo' })`
  color: red;
`;

render(<Comp filterThis="abc" passThru="def" />);

### Renders: <div className="[generated] foo" passThru="def"></div>

Thanks @​stevesims and all that contributed!

  • Add "transient props" API; https://github.com/styled-components/styled-components/pull/3052

    Think of transient props as a lightweight, but complementary API to shouldForwardProp. Because styled-components allows any kind of prop to be used for styling (a trait shared by most CSS-in-JS libraries, but not the third party library ecosystem in general), adding a filter for every possible prop you might use can get cumbersome.

    Transient props are a new pattern to pass props that are explicitly consumed only by styled components and are not meant to be passed down to deeper component layers. Here's how you use them:

    const Comp = styled.div`
  color: ${props => props.$fg || 'black'};
`;

render(<Comp $fg="red">I'm red!</Comp>);

    Note the dollar sign ($) prefix on the prop; this marks it as transient and styled-components knows not to add it to the rendered DOM element or pass it further down the component hierarchy.

Bugfixes

  • Fix slow SSR Rehydration for malformed CSS and increase fault-tolerance (see #​3018)

  • Change isPlainObject (internal method) to support objects created in a different context (see #​3068) thanks @​keeganstreet!

  • Add support for the <video disablePictureInPicture> (see #​3058) thanks @​egdbear!

v5.0.1

Compare Source

  • Added useTheme hook to named exports for react native (#​2982)

  • Performance enhancements

    • Refactored hashing function that is a bit faster in benchmarks (#​2983)
    • Fixed a bitwise math issue that was causing SSR performance degradations due to how we allocate typed arrays under the hood (#​2996)

  • Added some helpful new dev-time warnings for antipatterns

    • Recommending against usage of css @import inside createGlobalStyle and what to do instead (#​2997)
    • Catching and warning against dynamic creation of styled-components inside other component render paths (#​2998)

v5.0.0

Compare Source

It's finally here!!! 🚀See the migrating to v5 FAQ page for easy upgrade instructions!

Read the v5 release announcement!

TL;DR:

  • 19% smaller bundle size
  • 18% faster client-side mounting
  • 17% faster updating of dynamic styles
  • 45% faster server-side rendering
  • RTL support

...and much more all, with no breaking changes!

NOTE: At this time we recommend not using @import inside of createGlobalStyle. We're working on better behavior for this functionality but it just doesn't really work at the moment and it's better if you just embed these imports in your HTML index file, etc.

Changes
  • StyleSheetManager enhancements
    • you can now supply stylis plugins like stylis-plugin-rtl; <StyleSheetManager stylisPlugins={[]}>...</StyleSheetManager>
    • `disableVendor

Configuration

📅 Schedule: Branch creation - "on monday" (UTC), 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.

@renovate renovate bot requested a review from adamdecaf as a code owner February 20, 2023 04:03
@renovate
Copy link
Contributor Author

renovate bot commented Feb 20, 2023 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: webui/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @material-ui/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"18.2.0" from the root project
npm ERR!   peer react@"^18.2.0" from [email protected]
npm ERR!   node_modules/react-dom
npm ERR!     react-dom@"18.2.0" from the root project
npm ERR!     peer react-dom@">= 16.8.0" from [email protected]
npm ERR!     node_modules/styled-components
npm ERR!       dev styled-components@"6.1.1" from the root project
npm ERR!   2 more (react-scripts, styled-components)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0" from @material-ui/[email protected]
npm ERR! node_modules/@material-ui/core
npm ERR!   dev @material-ui/core@"4.12.4" from the root project
npm ERR!   peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm ERR!   node_modules/@material-ui/icons
npm ERR!     dev @material-ui/icons@"4.11.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0 || ^17.0.0" from @material-ui/[email protected]
npm ERR!   node_modules/@material-ui/core
npm ERR!     dev @material-ui/core@"4.12.4" from the root project
npm ERR!     peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm ERR!     node_modules/@material-ui/icons
npm ERR!       dev @material-ui/icons@"4.11.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/59a405/ea2a76/cache/others/npm/_logs/2023-11-14T15_17_37_576Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/59a405/ea2a76/cache/others/npm/_logs/2023-11-14T15_17_37_576Z-debug-0.log

@renovate Renovate
Copy link
Contributor Author

renovate bot commented Nov 14, 2023 •
edited
Loading

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@adamdecaf adamdecaf Awaiting requested review from adamdecaf adamdecaf is a code owner

At least 1 approving review is required to merge this pull request.

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
@renovate-bot