watchman
watchman copied to clipboard
chore(deps): update all (major)
This PR contains the following updates:
Package | Type | Update | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|---|---|
actions/checkout | action | major | v2 -> v3 |
||||
actions/download-artifact | action | major | v1 -> v3 |
||||
actions/setup-go | action | major | v2 -> v3 |
||||
actions/upload-artifact | action | major | v1 -> v3 |
||||
express-winston | dependencies | major | 3.4.0 -> 4.2.0 |
||||
github.com/mattn/go-sqlite3 | require | major | v1.14.15 -> v2.0.3+incompatible |
||||
history | dependencies | major | 4.10.1 -> 5.3.0 |
||||
http-proxy-middleware | dependencies | major | 0.21.0 -> 2.0.6 |
||||
quay.io/fedora/fedora | final | major | 37-x86_64 -> 38-x86_64 |
||||
quay.io/fedora/fedora | stage | major | 37-x86_64 -> 38-x86_64 |
||||
styled-components (source) | devDependencies | major | 4.4.1 -> 5.3.6 |
||||
tzinfo | major | "~> 1.2" -> "~> 2.0" |
Release Notes
actions/checkout
v3
bithavoc/express-winston
v4.2.0
v4.1.0
- 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
- Fix excess semicolon breaking Typescript compilation (#249)
v4.0.4
- Update lodash to 4.17.19 (#245)
- Update statusLevels to accept Boolean or StatusLevel object in TypeScript definition (#244)
v4.0.3
- Update lodash to 4.17.15 (#232)
- Add missing exceptionToMeta and skip to TypeScript definition (#234)
v4.0.2
- Add blacklist fields to BaseErrorLoggerOptions interface (#230)
v4.0.1
- Added
headerBlacklist
to BaseLoggerOptions for better typescript support (#228)
v4.0.0
- 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
andresponseField
options to allow storing the request and response in different metadata fields (or not at all) - Fixed
meta
configuration option onerrorLogger
(was not functioning at all) - Added .editorconfig and reformatted library to match
remix-run/history
v5.3.0
This release provides support for native ESM consumption of all exports.
v5.2.0
🐛 Bug fixes
- Fixed a few type declarations and deprecated the following types:
-
State
(now set tounknown
which will require consumer type narrowing) -
PartialPath
(usePartial<Path>
instead) -
PartialLocation
(usePartial<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: https://github.com/remix-run/history/compare/v5.1.0...v5.2.0
v5.1.0
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: https://github.com/remix-run/history/compare/v5.0.3...v5.1.0
v5.0.3
Fixed parsePath
adding incorrectly adding search
v5.0.2
Just a couple fixes:
- Fixed search params persisting on redirects
- Changed the
location.state
type toany
and removed the generic onLocation
Full Changelog: https://github.com/remix-run/history/compare/v5.0.1...v5.0.2
v5.0.1
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
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 withwindow.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
, andhashType
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
v2.0.6
- fix(proxyReqWs): catch socket errors (#763)
v2.0.5
- fix(error handler): add default handler to econnreset (#759)
v2.0.4
v2.0.3
- feat(package): optional @types/express peer dependency (#707)
v2.0.2
- chore(deps): update @types/http-proxy to 1.17.8 (#701)
- fix(fixRequestBody): fix request body for empty JSON object requests (#640) (mhassan1)
- fix(types): fix type regression (#700)
v2.0.1
- fix(fixRequestBody): fix type error (#615)
- test(coverage): improve coverage config (#609) (leonardobazico)
- test: add test coverage to fixRequestBody and responseInterceptor (#608) (leonardobazico)
- chore(typescript): extract handlers types (#603) (leonardobazico)
v2.0.0
- chore(package): drop node 10 [BREAKING CHANGE] (#577)
v1.3.1
v1.3.0
- docs(response interceptor): align with nodejs default utf8 (#567)
- feat: try to proxy body even after body-parser middleware (#492) (midgleyc)
v1.2.1
- fix(response interceptor): proxy original response headers (#563)
v1.2.0
- feat(handler): response interceptor (#520)
- fix(log error): handle undefined target when websocket errors (#527)
v1.1.2
- fix(log error): handle optional target (#523)
v1.1.1
- fix(error handler): re-throw http-proxy missing target error (#517)
- refactor(dependency): remove
camelcase
- fix(option): optional
target
whenrouter
is used (#512)
v1.1.0
- fix(errorHandler): fix confusing error message (#509)
- fix(proxy): close proxy when server closes (#508)
- refactor(lodash): remove lodash (#459) (#507) (TrySound)
- fix(ETIMEDOUT): return 504 on ETIMEDOUT (#480) (aremishevsky)
v1.0.6
- chore(deps): lodash 4.17.20 (#475)
v1.0.5
- chore(deps): lodash 4.17.19 (#454)
v1.0.4
- chore(deps): http-proxy 1.18.1 (#442)
v1.0.3
- build(package): exclude build artifact tsconfig.tsbuildinfo (#415)
v1.0.2
v1.0.1
v1.0.0
- 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
v5.3.6
What's Changed
- Fix statement on Ukraine by @Fer0x in https://github.com/styled-components/styled-components/pull/3724
- Fix/nonce in ssr by @samimakicc in https://github.com/styled-components/styled-components/pull/3755
New Contributors
- @samimakicc made their first contribution in https://github.com/styled-components/styled-components/pull/3755
Full Changelog: https://github.com/styled-components/styled-components/compare/v5.3.5...v5.3.6
v5.3.5
Add statement of solidarity against the war on Ukraine 🇺🇦
v5.3.3
What's Changed
- Backport #3568 (read from textContent rather than innerHTML during rehydrate) to v5 by @keeganstreet in https://github.com/styled-components/styled-components/pull/3591
- [v5] generate more complete sourcemaps by @henryqdineen in https://github.com/styled-components/styled-components/pull/3597
New Contributors
- @henryqdineen made their first contribution in https://github.com/styled-components/styled-components/pull/3597
Full Changelog: https://github.com/styled-components/styled-components/compare/v5.3.1...v5.3.3
v5.3.1
-
Fix forced server-side mode not triggering global styles (See #3566)
-
Fix SSR collisions caused by insufficient hash inputs and reordering of groups on the client, which is a regression in v5.2.0 (See #3563)
-
Fix dynamic creation React warning for React v18, backported to v5 by @lynndylanhurley (See #3564)
-
Add missing typeof window check when checking for duplicate instances of styled-components (See #3553)
-
Prevent ServerStyleSheet from emitting empty style tags, which would cause issues in IE11 (See #3555)
-
Support css tagged templates inside style objects, by @roginfarrer and @dvingo (See #3469)
v5.3.0
-
Pass
elementToBeCreated
as a third parameter toshouldForwardProp
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
fix an issue with an unguarded window accessor in a SSR path (see #3446)
v5.2.2
-
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
- 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
-
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 likestylis-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!
-
Allow
DISABLE_SPEEDY
to be set tofalse
to enable speedy mode in non-production environments (see #3289) thanks @FastFedora! -
Enable new style rules can be inserted in the middle of existing sheet when rendering on client after rehydrate.
GroupIDAllocator
is now changed to findnextFreeGroup
by checkingreverseRegister
, instead of setting it to the end of existing groups. (see #3233) thanks @mu29!
v5.1.1
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
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/3006Sometimes 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 thestyled()
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" />);
v5.0.1
-
Added useTheme hook to named exports for react native
-
Performance enhancements
- Refactored hashing function that is a bit faster in benchmarks
- Fixed a bitwise math issue that was causing SSR performance degradations due to how we allocate typed arrays under the hood
-
Added some helpful new dev-time warnings for antipatterns
- Recommending against usage of css
@import
insidecreateGlobalStyle
and what to do instead - Catching and warning against dynamic creation of styled-components inside other component render paths
- Recommending against usage of css
v5.0.0
Read the v5 release announcement!
- 19% smaller bundle size
- 18% faster client-side mounting
- 17% faster updating of dynamic styles
- 45% faster server-side rendering
- RTL support
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.
-
StyleSheetManager
enhancements- you can now supply stylis plugins like stylis-plugin-rtl;
<StyleSheetManager stylisPlugins={[]}>...</StyleSheetManager>
-
disableVendorPrefixes
removes autoprefixing if you don't need legacy browser support;<StyleSheetManager disableVendorPrefixes>...</StyleSheetManager>
-
disableCSSOMInjection
forces using the slower injection mode if other integrations in your runtime environment can't parse CSSOM-injected styles;<StyleSheetManager disableCSSOMInjection>...</StyleSheetManager>
- you can now supply stylis plugins like stylis-plugin-rtl;
-
Remove deprecated attrs "subfunction" syntax variant
styled.div.attrs({ color: p => p.color });
should become
styled.div.attrs(p => ({ color: p.color }));
You can still pass objects to
attrs
but individual properties shouldn't have functions that receive props anymore. -
Fix attrs not taking precedence over props when overriding a given prop
-
(ReactNative) upgrade css-to-react-native to v3 (changelog)
- Removed support for unitless line height in font shorthand
-
Replace
merge-anything
withmixin-deep
to save some bytes (this is what handles merging ofdefaultProps
between folded styled components); this is inlined into since the library is written in IE-incompatible syntax -
Fix certain adblockers messing up styling by purposefully not emitting the substring "ad" (case-insensitive) when generating dynamic class names
-
Fix regressed behavior between v3 and v4 where className was not correctly aggregated between folded
.attrs
invocations
- Fix support for styling custom elements (https://github.com/styled-components/styled-components/pull/2819)
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, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
⚠ Artifact update problem
Renovate failed to update artifacts 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: go.sum
Command failed: docker run --rm --name=renovate_sidecar --label=renovate_child -v "/mnt/renovate/gh/moov-io/watchman":"/mnt/renovate/gh/moov-io/watchman" -v "/tmp/renovate-cache":"/tmp/renovate-cache" -v "/tmp/containerbase":"/tmp/containerbase" -e GOPATH -e GOPROXY -e GOFLAGS -e CGO_ENABLED -e GIT_CONFIG_KEY_0 -e GIT_CONFIG_VALUE_0 -e GIT_CONFIG_KEY_1 -e GIT_CONFIG_VALUE_1 -e GIT_CONFIG_KEY_2 -e GIT_CONFIG_VALUE_2 -e GIT_CONFIG_COUNT -e BUILDPACK_CACHE_DIR -e CONTAINERBASE_CACHE_DIR -w "/mnt/renovate/gh/moov-io/watchman" docker.io/renovate/sidecar bash -l -c "install-tool golang 1.20.1 && go get -d -t ./..."
go: github.com/docker/docker/[email protected]+incompatible: missing github.com/docker/docker/go.mod and .../v23/go.mod at revision v23.0.1
File name: webui/package-lock.json
npm notice
npm notice New major version of npm available! 8.19.4 -> 9.5.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.5.0>
npm notice Run `npm install -g [email protected]` to update!
npm notice
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@"5.3.6" 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! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2023-02-16T12_40_05_558Z-debug-0.log