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.

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

chore(deps): update devdependencies (minor) #185

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 13, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@janus-idp/cli (source) 1.17.0 -> 1.19.1 age adoption passing confidence
@janus-idp/cli (source) 1.16.0 -> 1.19.1 age adoption passing confidence
@openapitools/openapi-generator-cli 2.13.4 -> 2.15.3 age adoption passing confidence
monaco-editor 0.50.0 -> 0.52.2 age adoption passing confidence
monaco-yaml (source) 5.1.1 -> 5.2.3 age adoption passing confidence
openapicmd (source) 2.3.2 -> 2.6.1 age adoption passing confidence
prettier (source) 3.3.3 -> 3.4.2 age adoption passing confidence
sass 1.77.2 -> 1.83.0 age adoption passing confidence
webpack 5.94.0 -> 5.97.1 age adoption passing confidence

Release Notes

janus-idp/backstage-plugins (@​janus-idp/cli)

v1.19.1

Compare Source

Patch Changes
  • 2d73fa1: fix(cli): support single packages better. This change fixes an issue in the package-dynamic-plugins command that prevents it from running properly in a single plugin project that does not have workspaces.

v1.19.0

Compare Source

Minor Changes
  • 9671df5: Bump packages/cli to 1.19.0 in main branch, in prep for release of 1.4.0
Patch Changes
  • 2acb6e0: fix(cli): add a flag to relax semver checks. This change updates the CLI to add an option to relax the semver checks on a per-package basis to cater for plugins where it is known there should be runtime compabability due to no interface changes.

  • 6d292af: fix(cli): adjust embedded module searching. The CLI attempts a require call to detect built embedded packages, this change adjusts the directory this require is attempted from to be at the level of discovered package instead of the dynamic plugin package.

  • 2ef4806: This change adds two new flags to handle native module dependencies.

    • --allow-native-package [package-name...]: flag to selectively allow native packages when exporting a dynamic plugin and allowing it's installation into the exported dynamic plugin.
    • --suppress-native-package [package-name..]: flag which replaces the native package with an empty package during export, preventing the native package's inclusion into the exported dynamic plugin's private dependencies.
  • 7643bda: fix(cli): redirect install output. This change updates the CLI so that stdout of the yarn install command is redirected to a file. This prevents a possible buffer overflow error that can occur but also gives the added benefit of making the install output available for troubleshooting should a dynamic plugin fail to export. On successful installation and plugin validation the yarn install log file will be removed.

v1.18.5

Compare Source

Patch Changes
  • 1277acb: fix(cli): add a flag to relax semver checks. This change updates the CLI to add an option to relax the semver checks on a per-package basis to cater for plugins where it is known there should be runtime compabability due to no interface changes.

v1.18.4

Compare Source

Patch Changes
  • 2bc9e4f: fix(cli): redirect install output. This change updates the CLI so that stdout of the yarn install command is redirected to a file. This prevents a possible buffer overflow error that can occur but also gives the added benefit of making the install output available for troubleshooting should a dynamic plugin fail to export. On successful installation and plugin validation the yarn install log file will be removed.

v1.18.3

Compare Source

Patch Changes
  • 318af8b: fix(cli): adjust embedded module searching. The CLI attempts a require call to detect built embedded packages, this change adjusts the directory this require is attempted from to be at the level of discovered package instead of the dynamic plugin package.

v1.18.2

Compare Source

Patch Changes
  • abd9dec: This change adds two new flags to handle native module dependencies.

    • --allow-native-package [package-name...]: flag to selectively allow native packages when exporting a dynamic plugin and allowing it's installation into the exported dynamic plugin.
    • --suppress-native-package [package-name..]: flag which replaces the native package with an empty package during export, preventing the native package's inclusion into the exported dynamic plugin's private dependencies.

v1.18.1

Compare Source

Patch Changes
  • e9b2878: fix(cli): fall back to using the cli script directly if a plugin package does not have an export-dynamic script

v1.18.0

Compare Source

Minor Changes
  • 8448c17: feat(cli) add flag to specify output directory

    This change adds an --export-to flag to the package-dynamic-plugins CLI command. This flag will skip the container build step, and instead copy the staged dynamic plugin assets to the specified output directory. The addition of this flag makes the --tag argument optional, and only required if --export-to is not specified.

Patch Changes
  • 8448c17: fix(cli): Improve example configuration display

    This change changes the CLI package-dynamic-plugins command to take
    advantage of some dynamic plugin projects that have followed the
    convention of maintaining a app-config.janus-idp.yaml in the root of the
    plugin source directory. When this file is present, it will be read in
    as the command processes dynamic plugins in the monorepo and then
    included in the example dynamic-plugins.yaml configuration printed out
    when the command successfully completes. This change also adjusts the
    control flow where this is printed out to ensure it's after successful
    completion of the container image.

v1.17.1

Compare Source

Patch Changes
  • 0e6bfd3: feat: update Backstage to the latest version

    Update to Backstage 1.32.5

OpenAPITools/openapi-generator-cli (@​openapitools/openapi-generator-cli)

v2.15.3

Compare Source

Bug Fixes

v2.15.2

Compare Source

Bug Fixes

v2.15.1

Compare Source

Bug Fixes

v2.15.0

Compare Source

Features
  • release: trigger a release (407e90f)

v2.14.1

Compare Source

Bug Fixes

v2.14.0

Compare Source

Features
  • config schema: add openapi-normalizer generator property (#​830) (c91d116)

v2.13.13

Compare Source

Bug Fixes

v2.13.12

Compare Source

Bug Fixes

v2.13.11

Compare Source

Bug Fixes

v2.13.10

Compare Source

Bug Fixes
  • deps: update dependency https-proxy-agent to v7.0.5 (#​800) (e8226d8)

v2.13.9

Compare Source

Bug Fixes

v2.13.8

Compare Source

Bug Fixes

v2.13.7

Compare Source

Bug Fixes

v2.13.6

Compare Source

Bug Fixes

v2.13.5

Compare Source

Bug Fixes
  • deps: update dependency axios to v1.7.4 [security] (#​789) (18abce4)
microsoft/monaco-editor (monaco-editor)

v0.52.2

Compare Source

Changes:

This list of changes was auto generated.

v0.52.0

Compare Source

  • Comment added inside of IModelContentChangedEvent

v0.51.0

Compare Source

  • New fields IEditorOptions.placeholder and IEditorOptions.compactMode
  • New fields IGotoLocationOptions.multipleTests and IGotoLocationOptions.alternativeTestsCommand
  • New field IInlineEditOptions.backgroundColoring
  • New experimental field IEditorOptions.experimental.useTrueInlineView
  • New options CommentThreadRevealOptions for comments

Contributions to monaco-editor:

remcohaszing/monaco-yaml (monaco-yaml)

v5.2.3

Compare Source

What's Changed

New Contributors

Full Changelog: remcohaszing/monaco-yaml@v5.2.2...v5.2.3

v5.2.2

Compare Source

  • fdd9417 Update monaco-languageserver-types to 0.4.0

Full Changelog: remcohaszing/monaco-yaml@v5.2.1...v5.2.2

v5.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: remcohaszing/monaco-yaml@v5.2.0...v5.2.1

v5.2.0

Compare Source

Full Changelog: remcohaszing/monaco-yaml@v5.1.1...v5.2.0

openapistack/openapicmd (openapicmd)

v2.6.1

Compare Source

v2.6.0

Compare Source

v2.5.2

Compare Source

v2.5.1

Compare Source

v2.5.0

Compare Source

v2.4.0

Compare Source

v2.3.3

Compare Source

prettier/prettier (prettier)

v3.4.2

Compare Source

diff

Treat U+30A0 & U+30FB in Katakana Block as CJK (#​16796 by @​tats-u)

Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.

<!-- Input (--prose-wrap=never) -->

C言
語
・
C++
・
Go
・
Rust

<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust

<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust

U+30A0 can be used as the replacement of the - in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン=サーンス”).

Fix comments print on class methods with decorators (#​16891 by @​fisker)
// Input
class A {
  @&#8203;decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.1
class A {
  @&#8203;decorator
  async /**
   * The method description
   *
   */
  method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.2
class A {
  @&#8203;decorator
  /**
   * The method description
   *
   */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}
Fix non-idempotent formatting (#​16899 by @​seiyab)

This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.

// Input
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.1 (first)
<div>
  foo
  <span>
    longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo
  </span>, abc
</div>;

// Prettier 3.4.1 (second)
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.2
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

v3.4.1

Compare Source

diff

Remove unnecessary parentheses around assignment in v-on (#​16887 by @​fisker)
<!-- Input -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

<!-- Prettier 3.4.0 -->
<template>
  <button @&#8203;click="(foo += 2)">Click</button>
</template>

<!-- Prettier 3.4.1 -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

v3.4.0

Compare Source

diff

🔗 Release Notes

sass/dart-sass (sass)

v1.83.0

Compare Source

  • Allow trailing commas in all argument and parameter lists.

v1.82.0

Compare Source

Command-Line Interface
  • Improve --watch mode reliability when making multiple changes at once, such
    as checking out a different Git branch.

  • Parse the calc-size() function as a calculation now that it's supported in
    some browsers.

Dart API
  • Add a SassCalculation.calcSize() function.

v1.81.1

Compare Source

  • No user-visible changes.

v1.81.0

Compare Source

  • Fix a few cases where deprecation warnings weren't being emitted for global
    built-in functions whose names overlap with CSS calculations.

  • Add support for the CSS round() calculation with a single argument, as long
    as that argument might be a unitless number.

v1.80.7

Compare Source

Embedded Host
  • Don't treat 0 as undefined for the green and blue channels in the
    LegacyColor constructor.

v1.80.6

Compare Source

Command-Line Interface
  • Make @parcel/watcher an optional dependency so this can still be installed
    on operating systems where it's unavailable.

v1.80.5

Compare Source

Embedded Host
  • Don't produce phantom @import deprecations when using an importer with the
    legacy API.

v1.80.4

Compare Source

  • No user-visible changes.

v1.80.3

Compare Source

  • Fix a bug where @import url("...") would crash in plain CSS files.

  • Improve consistency of how warnings are emitted by different parts of the
    compiler. This should result in minimal user-visible changes, but different
    types of warnings should now respond more reliably to flags like --quiet,
    --verbose, and --silence-deprecation.

v1.80.2

Compare Source

  • Fix a bug where deprecation warnings were incorrectly emitted for the
    plain-CSS invert() function.

v1.80.1

Compare Source

  • Fix a bug where repeated deprecation warnings were not automatically limited.

v1.80.0

Compare Source

  • @import is now officially deprecated, as are global built-in functions that
    are available within built-in modules. See the Sass blog post for more
    details on the deprecation process.
Embedded Host
  • Fix an error that would sometimes occur when deprecation warnings were
    emitted when using a custom importer with the legacy API.

v1.79.6

Compare Source

  • Fix a bug where Sass would add an extra */ after loud comments with
    whitespace after an explicit */ in the indented syntax.

  • Potentially breaking bug fix: Adding text after an explicit */ in the
    indented syntax is now an error, rather than silently generating invalid CSS.

Embedded Host
  • Properly export the SassBoolean type.

v1.79.5

Compare Source

  • Changes to how selector.unify() and @extend combine selectors:

    • The relative order of pseudo-classes (like :hover) and pseudo-elements
      (like ::before) within each original selector is now preserved when
      they're combined.

    • Pseudo selectors are now consistently placed at the end of the combined
      selector, regardless of which selector they came from. Previously, this
      reordering only applied to pseudo-selectors in the second selector.

  • Tweak the color transformation matrices for OKLab and OKLCH to match the
    newer, more accurate values in the CSS spec.

  • Fix a slight inaccuracy case when converting to srgb-linear and
    display-p3.

  • Potentially breaking bug fix: math.unit() now wraps multiple denominator
    units in parentheses. For example, px/(em*em) instead of px/em*em.

Command-Line Interface
  • Use @parcel/watcher to watch the filesystem when running from JavaScript and
    not using --poll. This should mitigate more frequent failures users have
    been seeing since version 4.0.0 of Chokidar, our previous watching tool, was
    released.
JS API
  • Fix SassColor.interpolate() to allow an undefined options parameter, as
    the types indicate.
Embedded Sass
  • Properly pass missing color channel values to and from custom functions.

v1.79.4

Compare Source

JS API
  • Fix a bug where passing green or blue to color.change() for legacy
    colors would fail.

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.
webpack/webpack (webpack)

v5.97.1

Compare Source

Bug Fixes
  • Performance regression
  • Sub define key should't be renamed when it's a defined variable

v5.97.0

Compare Source

v5.96.1

Compare Source

v5.96.0

Compare Source

Bug Fixes

  • Fixed Module Federation should track all referenced chunks
  • Handle Data URI without base64 word
  • HotUpdateChunk have correct runtime when modified with new runtime
  • Order of chunks ids in generated chunk code
  • No extra Javascript chunks when using asset module as an entrypoint
  • Use optimistically logic for output.environment.dynamicImport to determine chunk format when no browserslist or target
  • Collision with global variables for optimization.avoidEntryIife
  • Avoid through variables in inlined module
  • Allow chunk template strings in output.devtoolNamespace
  • No extra runtime for get javascript/css chunk filename
  • No extra runtime for prefetch and preload in JS runtime when it was unsed in CSS
  • Avoid cache invalidation using ProgressPlugin
  • Increase parallelism when using importModule on the execution stage
  • Correctly parsing string in export and import
  • Typescript types
  • [CSS] css/auto considers a module depending on its filename as css (pure CSS) or css/local, before it was css/global and css/local
  • [CSS] Always interpolate classes even if they are not involved in export
  • [CSS] No extra runtime in Javascript runtime chunks for asset modules used in CSS
  • [CSS] No extra runtime in Javascript runtime chunks for external asset modules used in CSS
  • [CSS] No extra runtime for the node target
  • [CSS] Fixed url()s and @import parsing
  • [CSS] Fixed - emit a warning on broken :local and :global

New Features

  • Export CSS and ESM runtime modules
  • Single Runtime Chunk and Federation e

Configuration

📅 Schedule: 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 is behind base branch, 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 Dec 13, 2024
@rhdh-bot rhdh-bot force-pushed the renovate/devdependencies-(minor) branch from 1bafd95 to 88b758d Compare December 13, 2024 16:14
@rhdh-gh-app
Copy link

rhdh-gh-app bot commented Dec 13, 2024

Changed Packages

Package Name Package Path Changeset Bump Current Version
@red-hat-developer-hub/backstage-plugin-bulk-import-backend workspaces/bulk-import/plugins/bulk-import-backend patch v5.2.0
@red-hat-developer-hub/backstage-plugin-bulk-import-common workspaces/bulk-import/plugins/bulk-import-common patch v1.4.1
@red-hat-developer-hub/backstage-plugin-bulk-import workspaces/bulk-import/plugins/bulk-import patch v1.10.6
@red-hat-developer-hub/backstage-plugin-lightspeed-backend workspaces/lightspeed/plugins/lightspeed-backend patch v0.2.1
@red-hat-developer-hub/backstage-plugin-lightspeed-common workspaces/lightspeed/plugins/lightspeed-common patch v0.1.2
@red-hat-developer-hub/backstage-plugin-lightspeed workspaces/lightspeed/plugins/lightspeed patch v0.2.4
@red-hat-developer-hub/backstage-plugin-openshift-image-registry workspaces/openshift-image-registry/plugins/openshift-image-registry patch v1.10.1
@red-hat-developer-hub/backstage-plugin-orchestrator-backend workspaces/orchestrator/plugins/orchestrator-backend patch v5.1.0
@red-hat-developer-hub/backstage-plugin-orchestrator-common workspaces/orchestrator/plugins/orchestrator-common patch v1.25.0
@red-hat-developer-hub/backstage-plugin-orchestrator-form-api workspaces/orchestrator/plugins/orchestrator-form-api patch v1.4.2
@red-hat-developer-hub/backstage-plugin-orchestrator-form-react workspaces/orchestrator/plugins/orchestrator-form-react patch v1.4.5
@red-hat-developer-hub/backstage-plugin-orchestrator-swf-editor-envelope workspaces/orchestrator/plugins/orchestrator-swf-editor-envelope patch v1.0.1
@red-hat-developer-hub/backstage-plugin-orchestrator workspaces/orchestrator/plugins/orchestrator patch v2.5.0

@renovate renovate bot force-pushed the renovate/devdependencies-(minor) branch from 88b758d to 8de257a Compare December 13, 2024 18:25
@rhdh-bot rhdh-bot force-pushed the renovate/devdependencies-(minor) branch from 8de257a to 0c5c9ec Compare December 13, 2024 18:25
@renovate renovate bot force-pushed the renovate/devdependencies-(minor) branch from 0c5c9ec to 026f76a Compare December 14, 2024 20:46
@rhdh-bot rhdh-bot force-pushed the renovate/devdependencies-(minor) branch from 026f76a to 88ef100 Compare December 14, 2024 20:46
@renovate renovate bot force-pushed the renovate/devdependencies-(minor) branch from 88ef100 to 00e4069 Compare December 14, 2024 20:51
@rhdh-bot rhdh-bot force-pushed the renovate/devdependencies-(minor) branch from 00e4069 to 924c5c8 Compare December 14, 2024 20:51
@renovate renovate bot force-pushed the renovate/devdependencies-(minor) branch from 924c5c8 to ab072c4 Compare December 16, 2024 00:33
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@rhdh-bot rhdh-bot force-pushed the renovate/devdependencies-(minor) branch from ab072c4 to 46af3b7 Compare December 16, 2024 00:33
@mareklibra mareklibra merged commit d59e940 into main Dec 16, 2024
15 checks passed
@renovate renovate bot deleted the renovate/devdependencies-(minor) branch December 16, 2024 08:06
christoph-jerolimov added a commit to christoph-jerolimov/rhdh-plugins that referenced this pull request Dec 16, 2024
christoph-jerolimov added a commit to christoph-jerolimov/rhdh-plugins that referenced this pull request Dec 16, 2024
christoph-jerolimov added a commit to christoph-jerolimov/rhdh-plugins that referenced this pull request Dec 16, 2024
christoph-jerolimov added a commit to christoph-jerolimov/rhdh-plugins that referenced this pull request Dec 16, 2024
christoph-jerolimov added a commit that referenced this pull request Dec 16, 2024
* chore: remove invalid entries of changesets from PR #185

* chore: remove invalid entries of changesets from PR #186

* chore: remove invalid entries of changesets from PR #201
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant