⬆️ Update all non-major dependencies #131
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/all-minor-patch"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
20.16.3
->20.16.5
5.1.3
->5.1.4
9.9.1
->9.10.0
9.27.0
->9.28.0
9.1.5
->9.1.6
5.8.0
->5.9.2
4.0.0
->4.0.2
9.9.0
->9.10.0
1.77.8
->1.79.1
5.5.4
->5.6.2
5.4.2
->5.4.6
2.0.5
->2.1.1
3.4.38
->3.5.6
4.4.3
->4.4.5
2.1.4
->2.1.6
3.7.1
->3.7.2
Release Notes
vitejs/vite-plugin-vue (@vitejs/plugin-vue)
v5.1.4
eslint/eslint (eslint)
v9.10.0
Compare Source
Features
301b90d
feat: Add types (#18854) (Nicholas C. Zakas)bcf0df5
feat: limit namespace import identifier in id-length rule (#18849) (ChaedongIm)45c18e1
feat: addrequireFlag
option torequire-unicode-regexp
rule (#18836) (Brett Zamir)183b459
feat: add error message for duplicate flags inno-invalid-regexp
(#18837) (Tanuj Kanti)c69b406
feat: report duplicate allowed flags inno-invalid-regexp
(#18754) (Tanuj Kanti)Documentation
bee0e7a
docs: update README (#18865) (Milos Djermanovic)5d80b59
docs: specify thatruleId
can benull
in custom formatter docs (#18857) (Milos Djermanovic)156b1c3
docs: Update README (GitHub Actions Bot)f6fdef9
docs: Update README (GitHub Actions Bot)a20c870
docs: Update README (GitHub Actions Bot)90e699b
docs: Update README (GitHub Actions Bot)Chores
24c3ff7
chore: upgrade to @eslint/js@9.10.0 (#18866) (Francesco Trotta)1ebdde1
chore: package.json update for @eslint/js release (Jenkins)e8fc5bd
chore: update dependency @eslint/core to ^0.5.0 (#18848) (renovate[bot])343f992
refactor: don't usenode.value
when removing unused directives (#18835) (Milos Djermanovic)3db18b0
refactor: Extract FileContext into class (#18831) (Nicholas C. Zakas)931d650
refactor: Use @eslint/plugin-kit (#18822) (Nicholas C. Zakas)ed5cf0c
chore: update dependency @eslint/json to ^0.4.0 (#18829) (Milos Djermanovic)d1f0831
chore: added missing ids (#18817) (Strek)ec92813
refactor: Config class (#18763) (Nicholas C. Zakas)vuejs/eslint-plugin-vue (eslint-plugin-vue)
v9.28.0
Compare Source
✨ Enhancements
New Rules
vue/max-props
rule that enforces the maximum number of props in Vue components.vue/require-default-export
rule that requires components to be thedefault
export.vue/max-template-depth
rule that enforces the maximum depth of<template>
.New Features
vue/define-macros-order
rule.additionalDirectives
option tovue/require-toggle-inside-transition
rule.🐛 Bug Fixes
vue/v-if-else-key
rule.vue/require-typed-object-prop
rule.v-model
directive invue/attribute-hyphenation
rule.vue/attribute-hyphenation
rule to skipv-bind.sync
.vue/no-deprecated-slot-attribute
rule to handlev-for
with dynamicslot
.vue/no-deprecated-slot-attribute
rule to skip dynamic components.⚙️ Updates
Full Changelog: https://github.com/vuejs/eslint-plugin-vue/compare/v9.27.0...v9.28.0
typicode/husky (husky)
v9.1.6
Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/typicode/husky/compare/v9.1.5...v9.1.6
panva/jose (jose)
v5.9.2
Compare Source
Refactor
v5.9.1
Compare Source
Fixes
v5.9.0
Compare Source
Features
prazdevs/pinia-plugin-persistedstate (pinia-plugin-persistedstate)
v4.0.2
Compare Source
compare changes
🩹 Fixes
CookieStorageOptions
from@nuxt/schema
rather thannuxt/schema
(9e77053)📖 Documentation
🏡 Chore
❤️ Contributors
v4.0.1
Compare Source
compare changes
🩹 Fixes
@nuxt/schema
rather thannuxt/schema
(#330)📖 Documentation
❤️ Contributors
pnpm/pnpm (pnpm)
v9.10.0
: pnpm 9.10Compare Source
Minor Changes
Support for a new CLI flag,
--exclude-peers
, added to thelist
andwhy
commands. When--exclude-peers
is used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #8506.Added a new setting to
package.json
atpnpm.auditConfig.ignoreGhsas
for ignoring vulnerabilities by their GHSA code #6838.For instance:
Patch Changes
Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
sass/dart-sass (sass)
v1.79.1
Compare Source
v1.79.0
Compare Source
Breaking change: Passing a number with unit
%
to the$alpha
parameterof
color.change()
,color.adjust()
,change-color()
, andadjust-color()
is now interpreted as a percentage, instead of ignoring the unit. For example,
color.change(red, $alpha: 50%)
now returnsrgb(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 thatcolor'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:
With the exception of legacy color spaces (
rgb
,hsl
, andhwb
), colorswill always be emitted in the color space they were defined in unless
they're explicitly converted.
The
color.to-space()
function is the only way to convert a color toanother 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 normalgamut of 0-255. These colors are always emitted using the
rgb()
syntax sothat 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()
, andlch()
functions;hwb()
function that matches the space-separated CSS syntax;color()
function that supports thesrgb
,srgb-linear
,display-p3
,a98-rgb
,prophoto-rgb
,rec2020
,xyz
,xyz-d50
, andxyz-d65
color spaces.Add new functions for working with color spaces:
color.to-space($color, $space)
converts$color
to the given$space
. Inmost 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
andhwb
spaces can't representout-of-gamut colors and so will be clamped.
color.channel($color, $channel, $space: null)
returns the value of thegiven
$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()
andcolor.hue()
.color.same($color1, $color2)
returns whether two colors represent the samecolor 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
isin-gamut for its color space (or
$space
if it's passed).color.to-gamut($color, $space: null)
returns$color
constrained to itsspace's gamut (or to
$space
's gamut, if passed). This is generally notrecommended 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 colorspace (
rgb
,hsl
, orhwb
).color.is-powerless($color, $channel, $space: null)
: Returns whether thegiven
$channel
of$color
is powerless in$space
(or its own colorspace). 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 ismissing in
$color
. Missing channels can be explicitly specified using thespecial value
none
and can appear automatically whencolor.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()
andcolor.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()
, andcolor.scale()
now support allchannels 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 thespace with the
$space
parameter. (For backwards-compatibility, thisdoesn'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()
andcolor.invert()
now support the standard CSS algorithmfor 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 likehsl
andoklch
,this parameter also allows you to specify how hue interpolation is handled.
color.complement()
now supports a$space
parameter that indicates whichcolor space should be used to take the complement.
color.grayscale()
now operates in theoklch
space for non-legacy colors.color.ie-hex-str()
now automatically converts its color to thergb
spaceand 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()
, andcolor.blackness()
functions, as well as their global counterparts, shouldbe replaced with calls to
color.channel()
.The global
adjust-hue()
,saturate()
,desaturate()
,lighten()
,darken()
,transaprentize()
,fade-out()
,opacify()
, andfade-in()
functions should be replaced by
color.adjust()
orcolor.scale()
.Add a
global-builtin
future deprecation, which can be opted-into with the--future-deprecation
flag or thefutureDeprecations
option in the JS orDart API. This emits warnings when any global built-in functions that are
now available in
sass:
modules are called. It will become active by defaultin an upcoming release alongside the
@import
deprecation.Dart API
Added a
ColorSpace
class which represents the various color spaces definedin the CSS spec.
Added
SassColor.space
which returns a color's color space.Added
SassColor.channels
and.channelsOrNull
which returns a listof 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 thecorresponding 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 ofSassColor.channel()
.Deprecated
SassColor.changeRgb()
,.changeHsl()
, and.changeHwb()
infavor of
SassColor.changeChannels()
.Added
SassNumber.convertValueToUnit()
as a shorthand forSassNumber.convertValue()
with a single numerator.Added
InterpolationMethod
andHueInterpolationMethod
which collectivelyrepresent 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
insilenceDeprecations
when usingthe legacy API.
Modify
SassColor
to accept a newspace
option, with support for all thenew 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 channelvalues, 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 thecorresponding names.
Deprecate
SassColor.red
,.green
,.blue
,.hue
,.saturation
,.lightness
,.whiteness
, and.blackness
in favor ofSassColor.channel()
.Embedded Sass
Add
Color
SassScript value, with support for all the new color spacesdefined in Color Level 4.
Remove
RgbColor
,HslColor
andHwbColor
SassScript values.v1.78.0
Compare Source
The
meta.feature-exists
function is now deprecated. This deprecation isnamed
feature-exists
.Fix a crash when using
@at-root
without any queries or children in theindented syntax.
JS API
Backport the deprecation options (
fatalDeprecations
,futureDeprecations
,and
silenceDeprecations
) to the legacy JS API. The legacy JS API is itselfdeprecated, 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 waspassed to the Sass API.
Embedded Sass
Explicitly expose a
sass
executable from thesass-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 justsass
whensass-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.
microsoft/TypeScript (typescript)
v5.6.2
: TypeScript 5.6Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
vitejs/vite (vite)
v5.4.6
Compare Source
Please refer to CHANGELOG.md for details.
v5.4.5
Compare Source
Please refer to CHANGELOG.md for details.
v5.4.4
Compare Source
Please refer to CHANGELOG.md for details.
v5.4.3
Compare Source
file://
reference (#17909) (561b940), closes #17909<template>
(#17988) (413c86a), closes #17988vitest-dev/vitest (vitest)
v2.1.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.1.0
Compare Source
This release makes another big change to the Browser Mode by introducing locators API:
You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the
page
object from@vitest/browser/context
.Potential Breaking Change
vitest.config.ts
orvite.config.ts
inside the folder)projects/*
will match anything inside theprojects
folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config.projects/**/*
previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects
.🚀 Features
userEvent.upload
in playwright provider - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6442 (cf148)--inspect
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6433 (0499a)--inspect-brk
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6434 (7ab0f)--exclude-after-remap
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6309 (5932a){ spy: true }
instead of a factory - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6289 (95f02)vi.advanceTimersToNextFrame
- by @bnjm and @sheremet-va in https://github.com/vitest-dev/vitest/issues/6347 (8ff63)🐞 Bug Fixes
index
file - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6266 (081cf)expect.getState().testPath
always returns correct path - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6472 (ac698)vitest
and@vitest/*
versions don't match - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6317 (e662c)vitenode
for uncovered files - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6044 (da52d)performance.now
instead ofDate.now
for duration - by @LuciNyan in https://github.com/vitest-dev/vitest/issues/6382 (fe489)toMatchInlineSnapshot
updates at the same location - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6332 (1606f)typecheck.include
overlaps withinclude
- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6256 (153ff)View changes on GitHub
vuejs/core (vue)
v3.5.6
Compare Source
Bug Fixes
once
option should be ignored by watchEffect (#11884) (49fa673)v3.5.5
Compare Source
Bug Fixes
72b7710010
to6d9d19f618
6d9d19f618
to0672d2bed4
0672d2bed4
to0b1a937023
0b1a937023
tob4660efe13
b4660efe13
tofb6a8e704c
fb6a8e704c
to9f496480c0
9f496480c0
tobb769feb81
bb769feb81
to53b41f1d46
53b41f1d46
tof12dc420ef
f12dc420ef
toaf220b778e
af220b778e
to71aba6ee7d
71aba6ee7d
to648a4dc78c