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

fix(deps): update all non-major dependencies with stable version (minor) #61

Closed
wants to merge 13 commits into from
Closed

fix(deps): update all non-major dependencies with stable version (minor) #61

wants to merge 13 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 7, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update Pending
express (source) ^4.18.3 -> ^4.21.0 age adoption passing confidence dependencies minor 4.21.1
node (source) 20.11.1 -> 20.17.0 age adoption passing confidence minor v20.18.0
node (source) 20.11.1 -> 20.17.0 age adoption passing confidence volta minor v20.18.0
pinia ^2.1.7 -> ^2.2.2 age adoption passing confidence dependencies minor 2.2.4 (+1)
postcss-html ^1.6.0 -> ^1.7.0 age adoption passing confidence devDependencies minor
sass ^1.70.0 -> ^1.79.3 age adoption passing confidence devDependencies minor 1.79.4
stylelint (source) ^16.2.1 -> ^16.9.0 age adoption passing confidence devDependencies minor
stylelint-config-recommended-scss ^14.0.0 -> ^14.1.0 age adoption passing confidence devDependencies minor
typescript (source) ~5.3.3 -> ~5.6.2 age adoption passing confidence devDependencies minor 5.6.3
vite (source) ^5.0.11 -> ^5.4.8 age adoption passing confidence devDependencies minor
vue-router ^4.2.5 -> ^4.4.5 age adoption passing confidence dependencies minor

Release Notes

expressjs/express (express)

v4.21.0

Compare Source

What's Changed

New Contributors

Full Changelog: expressjs/express@4.20.0...4.21.0

nodejs/node (node)

v20.17.0

Compare Source

v20.16.0

Compare Source

v20.15.1

Compare Source

v20.15.0: 2024-06-20, Version 20.15.0 'Iron' (LTS), @​marco-ippolito

Compare Source

test_runner: support test plans

It is now possible to count the number of assertions and subtests that are expected to run within a test. If the number of assertions and subtests that run does not match the expected count, the test will fail.

test('top level test', (t) => {
  t.plan(2);
  t.assert.ok('some relevant assertion here');
  t.subtest('subtest', () => {});
});

Contributed by Colin Ihrig in #​52860

inspector: introduce the --inspect-wait flag

This release introduces the --inspect-wait flag, which allows debugger to wait for attachement. This flag is useful when you want to debug the code from the beginning. Unlike --inspect-brk, which breaks on the first line, this flag waits for debugger to be connected and then runs the code as soon as a session is established.

Contributed by Kohei Ueno in #​52734

zlib: expose zlib.crc32()

This release exposes the crc32() function from zlib to user-land.

It computes a 32-bit Cyclic Redundancy Check checksum of data. If
value is specified, it is used as the starting value of the checksum,
otherwise, 0 is used as the starting value.

The CRC algorithm is designed to compute checksums and to detect error
in data transmission. It's not suitable for cryptographic authentication.

const zlib = require('node:zlib');
const { Buffer } = require('node:buffer');

let crc = zlib.crc32('hello');  // 907060870
crc = zlib.crc32('world', crc);  // 4192936109

crc = zlib.crc32(Buffer.from('hello', 'utf16le'));  // 1427272415
crc = zlib.crc32(Buffer.from('world', 'utf16le'), crc);  // 4150509955

Contributed by Joyee Cheung in #​52692

cli: allow running wasm in limited vmem with --disable-wasm-trap-handler

By default, Node.js enables trap-handler-based WebAssembly bound
checks. As a result, V8 does not need to insert inline bound checks
int the code compiled from WebAssembly which may speedup WebAssembly
execution significantly, but this optimization requires allocating
a big virtual memory cage (currently 10GB). If the Node.js process
does not have access to a large enough virtual memory address space
due to system configurations or hardware limitations, users won't
be able to run any WebAssembly that involves allocation in this
virtual memory cage and will see an out-of-memory error.

$ ulimit -v 5000000
$ node -p "new WebAssembly.Memory({ initial: 10, maximum: 100 });"
[eval]:1
new WebAssembly.Memory({ initial: 10, maximum: 100 });
^

RangeError: WebAssembly.Memory(): could not allocate memory
    at [eval]:1:1
    at runScriptInThisContext (node:internal/vm:209:10)
    at node:internal/process/execution:118:14
    at [eval]-wrapper:6:24
    at runScript (node:internal/process/execution:101:62)
    at evalScript (node:internal/process/execution:136:3)
    at node:internal/main/eval_string:49:3

--disable-wasm-trap-handler disables this optimization so that
users can at least run WebAssembly (with a less optimial performance)
when the virtual memory address space available to their Node.js
process is lower than what the V8 WebAssembly memory cage needs.

Contributed by Joyee Cheung in #​52766

Other Notable Changes
Commits

v20.14.0

Compare Source

v20.13.1: 2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Compare Source

2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Revert "tools: install npm PowerShell scripts on Windows"

Due to a regression in the npm installation on Windows, this commit reverts the change that installed npm PowerShell scripts on Windows.

Commits
  • [b7d80802cc] - Revert "tools: install npm PowerShell scripts on Windows" (marco-ippolito) #​52897

v20.13.0

Compare Source

v20.12.2: 2024-04-10, Version 20.12.2 'Iron' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes
  • CVE-2024-27980 - Command injection via args parameter of child_process.spawn without shell option enabled on Windows
Commits

v20.12.1

Compare Source

v20.12.0

Compare Source

vuejs/pinia (pinia)

v2.2.2

Compare Source

Please refer to CHANGELOG.md for details.

v2.2.1

Compare Source

Please refer to CHANGELOG.md for details.

v2.2.0

Compare Source

Please refer to CHANGELOG.md for details.

ota-meshi/postcss-html (postcss-html)

v1.7.0

Compare Source

What's Changed

Full Changelog: ota-meshi/postcss-html@v1.6.0...v1.7.0

sass/dart-sass (sass)

v1.79.3

Compare Source

  • Update the $channel parameter in the suggested replacement for
    color.red(), color.green(), color.blue(), color.hue(),
    color.saturation(), color.lightness(), color.whiteness(), and
    color.blackness() to use a quoted string.

v1.79.2

Compare Source

  • Add a $space parameter to the suggested replacement for color.red(),
    color.green(), color.blue(), color.hue(), color.saturation(),
    color.lightness(), color.whiteness(), and color.blackness().

  • Update deprecation warnings for the legacy JS API to include a link to
    relevant documentation.

v1.79.1

Compare Source

  • No user-visible changes.

v1.79.0

Compare Source

  • Breaking change: Passing a number with unit % to the $alpha parameter
    of color.change(), color.adjust(), change-color(), and adjust-color()
    is now interpreted as a percentage, instead of ignoring the unit. For example,
    color.change(red, $alpha: 50%) now returns rgb(255 0 0 / 0.5).

  • Potentially breaking compatibility fix: Sass no longer rounds RGB channels
    to the nearest integer. This means that, for example, rgb(0 0 1) != rgb(0 0 0.6). This matches the latest version of the CSS spec and browser behavior.

  • Potentially breaking compatibility fix: Passing large positive or negative
    values to color.adjust() can now cause a color's channels to go outside that
    color's gamut. In most cases this will currently be clipped by the browser and
    end up showing the same color as before, but once browsers implement gamut
    mapping it may produce a different result.

  • Add support for CSS Color Level 4 color spaces. Each color value now tracks
    its color space along with the values of each channel in that color space.
    There are two general principles to keep in mind when dealing with new color
    spaces:

    1. With the exception of legacy color spaces (rgb, hsl, and hwb), colors
      will always be emitted in the color space they were defined in unless
      they're explicitly converted.

    2. The color.to-space() function is the only way to convert a color to
      another color space. Some built-in functions may do operations in a
      different color space, but they'll always convert back to the original space
      afterwards.

  • rgb colors can now have non-integer channels and channels outside the normal
    gamut of 0-255. These colors are always emitted using the rgb() syntax so
    that modern browsers that are being displayed on wide-gamut devices can
    display the most accurate color possible.

  • Add support for all the new color syntax defined in Color Level 4, including:

    • oklab(), oklch(), lab(), and lch() functions;
    • a top-level hwb() function that matches the space-separated CSS syntax;
    • and a color() function that supports the srgb, srgb-linear,
      display-p3, a98-rgb, prophoto-rgb, rec2020, xyz, xyz-d50, and
      xyz-d65 color spaces.

  • Add new functions for working with color spaces:

    • color.to-space($color, $space) converts $color to the given $space. In
      most cases this conversion is lossless—the color may end up out-of-gamut for
      the destination color space, but browsers will generally display it as best
      they can regardless. However, the hsl and hwb spaces can't represent
      out-of-gamut colors and so will be clamped.

    • color.channel($color, $channel, $space: null) returns the value of the
      given $channel in $color, after converting it to $space if necessary.
      It should be used instead of the old channel-specific functions such as
      color.red() and color.hue().

    • color.same($color1, $color2) returns whether two colors represent the same
      color even across color spaces. It differs from $color1 == $color2 because
      == never consider colors in different (non-legacy) spaces as equal.

    • color.is-in-gamut($color, $space: null) returns whether $color is
      in-gamut for its color space (or $space if it's passed).

    • color.to-gamut($color, $space: null) returns $color constrained to its
      space's gamut (or to $space's gamut, if passed). This is generally not
      recommended since even older browsers will display out-of-gamut colors as
      best they can, but it may be necessary in some cases.

    • color.space($color): Returns the name of $color's color space.

    • color.is-legacy($color): Returns whether $color is in a legacy color
      space (rgb, hsl, or hwb).

    • color.is-powerless($color, $channel, $space: null): Returns whether the
      given $channel of $color is powerless in $space (or its own color
      space). A channel is "powerless" if its value doesn't affect the way the
      color is displayed, such as hue for a color with 0 chroma.

    • color.is-missing($color, $channel): Returns whether $channel's value is
      missing in $color. Missing channels can be explicitly specified using the
      special value none and can appear automatically when color.to-space()
      returns a color with a powerless channel. Missing channels are usually
      treated as 0, except when interpolating between two colors and in
      color.mix() where they're treated as the same value as the other color.

  • Update existing functions to support color spaces:

    • hsl() and color.hwb() no longer forbid out-of-bounds values. Instead,
      they follow the CSS spec by clamping them to within the allowed range.

    • color.change(), color.adjust(), and color.scale() now support all
      channels of all color spaces. However, if you want to modify a channel
      that's not in $color's own color space, you have to explicitly specify the
      space with the $space parameter. (For backwards-compatibility, this
      doesn't apply to legacy channels of legacy colors—for example, you can still
      adjust an rgb color's saturation without passing $space: hsl).

    • color.mix() and color.invert() now support the standard CSS algorithm
      for interpolating between two colors (the same one that's used for gradients
      and animations). To use this, pass the color space to use for interpolation
      to the $method parameter. For polar color spaces like hsl and oklch,
      this parameter also allows you to specify how hue interpolation is handled.

    • color.complement() now supports a $space parameter that indicates which
      color space should be used to take the complement.

    • color.grayscale() now operates in the oklch space for non-legacy colors.

    • color.ie-hex-str() now automatically converts its color to the rgb space
      and gamut-maps it so that it can continue to take colors from any color
      space.

  • The following functions are now deprecated, and uses should be replaced with
    the new color-space-aware functions defined above:

    • The color.red(), color.green(), color.blue(), color.hue(),
      color.saturation(), color.lightness(), color.whiteness(), and
      color.blackness() functions, as well as their global counterparts, should
      be replaced with calls to color.channel().

    • The global adjust-hue(), saturate(), desaturate(), lighten(),
      darken(), transaprentize(), fade-out(), opacify(), and fade-in()
      functions should be replaced by color.adjust() or color.scale().

  • Add a global-builtin future deprecation, which can be opted-into with the
    --future-deprecation flag or the futureDeprecations option in the JS or
    Dart API. This emits warnings when any global built-in functions that are
    now available in sass: modules are called. It will become active by default
    in an upcoming release alongside the @import deprecation.

Dart API

  • Added a ColorSpace class which represents the various color spaces defined
    in the CSS spec.

  • Added SassColor.space which returns a color's color space.

  • Added SassColor.channels and .channelsOrNull which returns a list
    of channel values, with missing channels converted to 0 or exposed as null,
    respectively.

  • Added SassColor.isLegacy, .isInGamut, .channel(), .isChannelMissing(),
    .isChannelPowerless(), .toSpace(), .toGamut(), .changeChannels(), and
    .interpolate() which do the same thing as the Sass functions of the
    corresponding names.

  • SassColor.rgb() now allows out-of-bounds and non-integer arguments.

  • SassColor.hsl() and .hwb() now allow out-of-bounds arguments.

  • Added SassColor.hwb(), .srgb(), .srgbLinear(), .displayP3(),
    .a98Rgb(), .prophotoRgb(), .rec2020(), .xyzD50(), .xyzD65(),
    .lab(), .lch(), .oklab(), .oklch(), and .forSpace() constructors.

  • Deprecated SassColor.red, .green, .blue, .hue, .saturation,
    .lightness, .whiteness, and .blackness in favor of
    SassColor.channel().

  • Deprecated SassColor.changeRgb(), .changeHsl(), and .changeHwb() in
    favor of SassColor.changeChannels().

  • Added SassNumber.convertValueToUnit() as a shorthand for
    SassNumber.convertValue() with a single numerator.

  • Added InterpolationMethod and HueInterpolationMethod which collectively
    represent the method to use to interpolate two colors.

JS API

  • While the legacy API has been deprecated since we released the modern API, we
    now emit warnings when the legacy API is used to make sure users are aware
    that it will be removed in Dart Sass 2.0.0. In the meantime, you can silence
    these warnings by passing legacy-js-api in silenceDeprecations when using
    the legacy API.

  • Modify SassColor to accept a new space option, with support for all the
    new color spaces defined in Color Level 4.

  • Add SassColor.space which returns a color's color space.

  • Add SassColor.channels and .channelsOrNull which returns a list of channel
    values, with missing channels converted to 0 or exposed as null, respectively.

  • Add SassColor.isLegacy, .isInGamut(), .channel(), .isChannelMissing(),
    .isChannelPowerless(), .toSpace(), .toGamut(), .change(), and
    .interpolate() which do the same thing as the Sass functions of the
    corresponding names.

  • Deprecate SassColor.red, .green, .blue, .hue, .saturation,
    .lightness, .whiteness, and .blackness in favor of
    SassColor.channel().

Embedded Sass

  • Add Color SassScript value, with support for all the new color spaces
    defined in Color Level 4.

  • Remove RgbColor, HslColor and HwbColor SassScript values.

v1.78.0

Compare Source

  • The meta.feature-exists function is now deprecated. This deprecation is
    named feature-exists.

  • Fix a crash when using @at-root without any queries or children in the
    indented syntax.

JS API

  • Backport the deprecation options (fatalDeprecations, futureDeprecations,
    and silenceDeprecations) to the legacy JS API. The legacy JS API is itself
    deprecated, and you should move off of it if possible, but this will allow
    users of bundlers and other tools that are still using the legacy API to
    still control deprecation warnings.

  • Fix a bug where accessing SourceSpan.url would crash when a relative URL was
    passed to the Sass API.

Embedded Sass

  • Explicitly expose a sass executable from the sass-embedded npm package.
    This was intended to be included in 1.63.0, but due to the way
    platform-specific dependency executables are installed it did not work as
    intended. Now users can run npx sass for local installs or just sass when
    sass-embedded is installed globally.

  • Add linux-riscv64, linux-musl-riscv64, and android-riscv64 support for the
    sass-embedded npm package.

  • Fix an edge case where the Dart VM could hang when shutting down when requests
    were in flight.

  • Fix a race condition where the embedded host could fail to shut down if it was
    closed around the same time a new compilation was started.

  • Fix a bug where parse-time deprecation warnings could not be controlled by
    the deprecation options in some circumstances.

v1.77.8

Compare Source

  • No user-visible changes.

v1.77.7

Compare Source

  • Declarations that appear after nested rules are deprecated, because the
    semantics Sass has historically used are different from the semantics
    specified by CSS. In the future, Sass will adopt the standard CSS semantics.

    See the Sass website for details.

  • Potentially breaking bug fix: // in certain places such as unknown
    at-rule values was being preserved in the CSS output, leading to potentially
    invalid CSS. It's now properly parsed as a silent comment and omitted from the
    CSS output.

v1.77.6

Compare Source

  • Fix a few cases where comments and occasionally even whitespace wasn't allowed
    between the end of Sass statements and the following semicolon.

v1.77.5

Compare Source

  • Fully trim redundant selectors generated by @extend.

v1.77.4

Compare Source

Embedded Sass

  • Support passing Version input for fatalDeprecations as string over
    embedded protocol.

  • Fix a bug in the JS Embedded Host where Version could be incorrectly accepted
    as input for silenceDeprecations and futureDeprecations in pure JS.

v1.77.3

Compare Source

Dart API
  • Deprecation.duplicateVariableFlags has been deprecated and replaced with
    Deprecation.duplicateVarFlags to make it consistent with the
    duplicate-var-flags name used on the command line and in the JS API.

v1.77.2

Compare Source

  • Don't emit deprecation warnings for functions and mixins beginning with __.

  • Allow user-defined functions whose names begin with _ and otherwise look
    like vendor-prefixed functions with special CSS syntax.

Command-Line Interface

  • Properly handle the --silence-deprecation flag.

  • Handle the --fatal-deprecation and --future-deprecation flags for
    --interactive mode.

v1.77.1

Compare Source

  • Fix a crash that could come up with importers in certain contexts.

v1.77.0

Compare Source

  • Don't throw errors for at-rules in keyframe blocks.

v1.76.0

Compare Source

  • Throw errors for misplaced statements in keyframe blocks.

  • Mixins and functions whose names begin with -- are now deprecated for
    forwards-compatibility with the in-progress CSS functions and mixins spec.
    This deprecation is named css-function-mixin.

v1.75.0

Compare Source

  • Fix a bug in which stylesheet canonicalization could be cached incorrectly
    when custom importers or the Node.js package importer made decisions based on
    the URL of the containing stylesheet.
JS API
  • Allow importer to be passed without url in StringOptionsWithImporter.

v1.74.1

Compare Source

  • No user-visible changes.

v1.72.0

Compare Source

  • Support adjacent /s without whitespace in between when parsing plain CSS
    expressions.

  • Allow the Node.js pkg: importer to load Sass stylesheets for package.json
    exports field entries without extensions.

  • When printing suggestions for variables, use underscores in variable names
    when the original usage used underscores.

JavaScript API
  • Properly resolve pkg: imports with the Node.js package importer when
    arguments are passed to the JavaScript process.

v1.71.1

Compare Source

Command-Line Interface
  • Ship the musl Linux release with the proper Dart executable.
JavaScript API

  • Export the NodePackageImporter class in ESM mode.

  • Allow `NodePackageIm

Configuration

📅 Schedule: Branch creation - "before 5am every weekday" in timezone America/New_York, Automerge - "every weekday" in timezone America/New_York.

🚦 Automerge: Enabled.

♻ 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jun 7, 2024
@renovate renovate bot requested a review from a team as a code owner June 7, 2024 06:16
@renovate renovate bot added the renovate-bot label Jun 7, 2024
kongponents-bot
kongponents-bot previously approved these changes Jun 7, 2024
View reviewed changes
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from dcc1065 to dba56ee Compare June 10, 2024 06:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from dba56ee to 6641164 Compare June 11, 2024 04:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6641164 to 54f7413 Compare June 13, 2024 05:10
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 54f7413 to 6b61672 Compare June 14, 2024 04:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6b61672 to a428342 Compare June 17, 2024 07:25
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a428342 to e7276e1 Compare June 21, 2024 07:07
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e7276e1 to 8937126 Compare June 24, 2024 07:41
@renovate
fix(deps): update dependency body-parser to v1.20.3 [security] (#71)
628f6d2 
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
chore(deps): update eslint (#75)
2184be3 
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
chore(deps): update dependency vite to v5.1.8 [security] (#69)
f8e666e 
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
fix(deps): update dependency axios to v1.7.4 [security] (#67)
48879e3 
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8ddd5fd to 4c1e6f7 Compare October 2, 2024 06:24
kongponents-bot
kongponents-bot previously approved these changes Oct 2, 2024
View reviewed changes
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4c1e6f7 to 2f4544a Compare October 3, 2024 06:49
kongponents-bot
kongponents-bot previously approved these changes Oct 3, 2024
View reviewed changes
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2f4544a to 74baff4 Compare October 7, 2024 06:57
kongponents-bot
kongponents-bot previously approved these changes Oct 7, 2024
View reviewed changes
renovate bot added 3 commits October 9, 2024 16:20
@renovate
chore(deps): update vitest monorepo to v2 (#66)
f76c046 
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
chore(deps): update dependency eslint to ^9.11.1 (#74)
c568109 
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
fix(deps): update all non-major dependencies with stable version
358ec96
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 74baff4 to 358ec96 Compare October 9, 2024 20:22
@renovate renovate bot changed the title chore(deps): update all non-major dependencies with stable version (minor) fix(deps): update all non-major dependencies with stable version (minor) Oct 9, 2024
@adamdehaven adamdehaven closed this Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kongponents-bot kongponents-bot kongponents-bot approved these changes

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

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

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file renovate-bot
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@kongponents-bot @adamdehaven