Skip to content

fix(deps): update npm minor and patch dependencies - #283

Open
red-hat-konflux[bot] wants to merge 1 commit into
masterfrom
konflux/mintmaker/master/npm-minor-and-patch-dependencies
Open

fix(deps): update npm minor and patch dependencies#283
red-hat-konflux[bot] wants to merge 1 commit into
masterfrom
konflux/mintmaker/master/npm-minor-and-patch-dependencies

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented May 28, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@patternfly/react-core ^6.4.3^6.6.1 age confidence
@patternfly/react-icons ^6.0.0^6.6.1 age confidence
@patternfly/react-table (source) ^6.4.3^6.6.1 age confidence
axios (source) ^1.8.3^1.20.0 age confidence
history ^5.0.0^5.3.0 age confidence
humanize-duration 3.28.03.34.1 age confidence
react-redux ^8.1.0^8.1.3 age confidence
react-router-dom (source) ^6.30.0^6.30.6 age confidence
redux (source) ^4.2.0^4.2.1 age confidence
sass 1.94.21.104.0 age confidence

Release Notes

patternfly/patternfly-react (@​patternfly/react-core)

v6.6.1

Compare Source

v6.6.0

Compare Source

axios/axios (axios)

v1.20.0

Compare Source

v1.20.0 — August 19, 2026

This release hardens runtime option handling, adds RFC 9110 status-code aliases, fixes Node.js and XHR reliability issues, and refreshes project tooling and documentation.

⚠️ Breaking Changes & Deprecations

  • HTTP Status Naming: Added ContentTooLarge (413) and UnprocessableContent (422), while retaining PayloadTooLarge and UnprocessableEntity as backward-compatible deprecated aliases. (#​11082)

🔒 Security Fixes

  • Runtime Option Handling: Hardened behavioral configuration reads against shared and foreign prototype pollution and normalized unsafe interceptor replacement objects. This also clarifies Fetch redirect and custom implementation behavior, HTTP/2 DNS and proxy handling, CIDR-based NO_PROXY matching, and malformed data URI rejection; see the PR for documented compatibility effects. (#​11141)

🐛 Bug Fixes

  • Interceptor Lifecycle: Prevented unbounded handler-array growth by trimming trailing ejected interceptors without changing iteration semantics, and kept interceptor operations safe when the public handlers field is nullish. (#​11087, #​11118)
  • Request Error Preservation: Prevented custom Error.prepareStackTrace implementations that return non-string values from replacing the original request failure with an unrelated TypeError. (#​11109)
  • XHR Reliability: Navigation-canceled requests now reject with ECONNABORTED instead of resolving with status 0, while successful downloads flush their final progress callback during the live loadend dispatch. (#​11094, #​11121)
  • Node.js Socket Memory: Removed request-context retention from per-socket error listeners, preventing completed response data from being pinned for the lifetime of pooled keep-alive sockets. (#​11091)
  • Core Methods and HTTP Errors: Prevented structural method-header buckets from leaking into outgoing headers, standardized invalid DNS lookup and httpVersion failures as AxiosError.ERR_BAD_OPTION_VALUE, and corrected the timeoutErrorMessage merge strategy. (#​11096)

🔧 Maintenance & Chores

🌟 New Contributors

We are thrilled to welcome our new contributors. Thank you for helping improve axios:

Full Changelog (axios/axios@v1.19.0...v1.20.0)

v1.19.0

Compare Source

This release raises the form-data security floor, adds configuration and type-system capabilities, and fixes NO_PROXY matching, interceptor errors, progress reporting, and serialization edge cases.

v1.18.1

Compare Source

v1.18.1 — June 21, 2026

This release focuses on Node HTTP adapter fixes, safer AxiosError serialisation, runtime/type correctness fixes, documentation updates, and dependency maintenance.

🐛 Bug Fixes

  • AxiosError Serialisation: Made AxiosError#cause non-enumerable to prevent circular JSON serialisation failures when errors include nested causes. (#​10913)
  • Node HTTP Adapter: Guarded socket.setKeepAlive for proxy agent streams, accepted path-only URLs when socketPath is configured, deferred environment proxy handling to Node, and explicitly passed maxBodyLength through to follow-redirects. (#​10917, #​10930, #​10942, #​10993)
  • Runtime and Type Correctness: Fixed several runtime crashes, type definition mismatches, and incorrect error handling paths. (#​10959, #​11021)
  • AxiosURLSearchParams: Switched the encoder callback to an arrow function so encoder.call(this) receives the AxiosURLSearchParams instance correctly. (#​11019)

🔧 Maintenance & Chores

🌟 New Contributors

We are thrilled to welcome our new contributors. Thank you for helping improve axios:

Full Changelog

EvanHahn/HumanizeDuration.js (humanize-duration)

v3.34.1

Compare Source

  • fix: Arabic (and other languages with digitReplacements) better handle large numbers

v3.34.0

Compare Source

  • new: Norwegian Nynorsk support (nn)
  • fix: Lithuanian now uses the singular form for counts such as 101 and 201 (for example "101 diena" instead of "101 dienų")

v3.33.2

Compare Source

  • fix: Romanian now correctly uses "de" before nouns for numbers >= 20 such as "20 de minute" instead of "20 minute" (see #​235)

v3.33.1

Compare Source

  • change: shrink size slightly

v3.33.0

Compare Source

  • new: Serbian Latin support (sr_Latn)

v3.32.2

Compare Source

  • fix: use "週間" instead of "週" in Japanese (see #​230)

v3.32.1

Compare Source

  • fix: hide unit count if 2 in Arabic (see #​222)

v3.32.0

Compare Source

  • new: Amharic support (am)
  • change: use Object.assign internally on newer runtimes, which should be slightly faster

v3.31.0

Compare Source

  • new: Central Kurdish support (ckb)

v3.30.0

Compare Source

  • new: Uzbek support (uz and uz_CYR)

v3.29.0

Compare Source

  • new: digitReplacements option
  • change: cleaned up documentation
  • change: shrank package size slightly
sass/dart-sass (sass)

v1.104.0

Compare Source

  • Potentially breaking compatibility fix: Colors now convert the special
    values NaN and negative zero, as well as infinity and negative infinity for
    polar-hue channels, to 0 as per the CSS spec.

  • The special value negative zero is now serialized as -0 instead of 0 for
    greater compatibility when using it in CSS calculations.

v1.103.1

Compare Source

  • No user-visible changes.

v1.103.0

Compare Source

  • Potentially breaking compatibility fix: Colors now preserve "analogous
    sets" of missing channels during conversions, per the CSS spec. For example,
    color.to-space(lch(50% none none), lab) now returns lab(50% none none)
    instead of lab(50% 0 0).

v1.102.0

Compare Source

  • Use the 2.4 gamma transfer function for rec2020, as specified by the latest
    draft of CSS Color 4.

v1.101.7

Compare Source

  • No user-visible changes.

v1.101.6

Compare Source

  • No user-visible changes.

v1.101.5

Compare Source

  • No user-visible changes.

v1.101.4

Compare Source

  • Avoid emitting rgb() or rgba() functions with non-percent decimal
    channels. Older browsers only support integer values or (potentially decimal)
    percentages for these functions, so in order to preserve
    backwards-compatibility while retaining full precision for modern browsers,
    legacy colors that contain at least one non-integer channel will now use
    percentages for their channels (for example, rgb(0%, 100%, 50%) rather than
    rgb(0, 255, 127.5)).

  • Fix a bug where the values of plain-CSS if() expressions were emitted using
    their meta.inspect() format rather than their CSS serialization format.

v1.101.3

Compare Source

  • No user-visible changes.

v1.101.0

Compare Source

  • Potentially breaking bug fix: The Node package importer now properly
    supports resolving import-only variants of Sass files declared in the
    exports, sass, and style fields of package.json. Previously, these
    files were ignored even when loaded via @import, so any code relying on
    loading module-system-only files this way may break.

v1.100.0

Compare Source

  • Writing two compound selectors adjacent to one another without any whitespace
    between them, such as [class]a, is now deprecated. This was always an error
    in CSS and Sass only supported it by mistake.

    See the Sass website for
    details.

v1.99.0

Compare Source

  • Add support for parent selectors (&) at the root of the document. These are
    emitted as-is in the CSS output, where they're interpreted as the scoping
    root
    .

  • User-defined functions named calc or clamp are no longer forbidden. If
    such a function exists without a namespace in the current module, it will be
    used instead of the built-in calc() or clamp() function.

  • User-defined functions whose names begin with - and end with -expression,
    -url, -and, -or, or -not are no longer forbidden. These were
    originally intended to match vendor prefixes, but in practice no vendor
    prefixes for these functions ever existed in real browsers.

  • User-defined functions named EXPRESSION, URL, and ELEMENT, those that
    begin with - and end with -ELEMENT, as well as the same names with some
    lowercase letters are now deprecated, These are names conflict with plain CSS
    functions that have special syntax.

    See the Sass website for details.

  • In a future release, calls to functions whose names begin with - and end
    with -expression and -url will no longer have special parsing. For now,
    these calls are deprecated if their behavior will change in the future.

    See the Sass website for details.

  • Calls to functions whose names begin with - and end with -progid:... are
    deprecated.

    See the Sass website for details.

v1.98.0

Compare Source

Command-Line Interface
  • Gracefully handle dependency loops in --watch mode.
Dart API
  • Add a const Logger.defaultLogger field. This provides a logger that emits to
    standard error or the browser console, but automatically chooses whether to
    use terminal colors.
JavaScript API
  • Fix a crash when manually constructing a SassCalculation for 'calc' with
    an argument that can't be simplified.

  • Properly emit deprecation warnings as text rather than StringBuffer objects
    when running in a browser.

  • Emit colored warnings and other messages on the console when running in a
    browser.

v1.97.3

Compare Source

  • Fix a bug where nesting an at-rule within multiple style rules in plain CSS
    could cause outer style rules to be omitted.

v1.97.2

Compare Source

  • Additional fixes for implicit configuration when nested imports are involved.

v1.97.1

Compare Source

  • Fix a bug with the new CSS-style if() syntax where values would be evaluated
    even if their conditions didn't match.

v1.97.0

Compare Source

  • Add support for the display-p3-linear color space.

v1.96.0

Compare Source

  • Allow numbers with complex units (more than one numerator unit or more than
    zero denominator units) to be emitted to CSS. These are now emitted as
    calc() expressions, which now support complex units in plain CSS.

v1.95.1

Compare Source

  • No user-visible changes.

v1.95.0

Compare Source

  • Add support for the CSS-style if() function. In addition to supporting the
    plain CSS syntax, this also supports a sass() query that takes a Sass
    expression that evaluates to true or false at preprocessing time depending
    on whether the Sass value is truthy. If there are no plain-CSS queries, the
    function will return the first value whose query returns true during
    preprocessing. For example, if(sass(false): 1; sass(true): 2; else: 3)
    returns 2.

  • The old Sass if() syntax is now deprecated. Users are encouraged to migrate
    to the new CSS syntax. if($condition, $if-true, $if-false) can be changed to
    if(sass($condition): $if-true; else: $if-false).

    See the Sass website for details.

  • Plain-CSS if() functions are now considered "special numbers", meaning that
    they can be used in place of arguments to CSS color functions.

  • Plain-CSS if() functions and attr() functions are now considered "special
    variable strings" (like var()), meaning they can now be used in place of
    multiple arguments or syntax fragments in various CSS functions.

v1.94.3

Compare Source

  • Fix the span reported for standalone % expressions followed by whitespace.

Configuration

📅 Schedule: (UTC)

  • 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

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux
red-hat-konflux Bot requested a review from a team as a code owner May 28, 2026 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants