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

fix: update npm #1481

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: update npm #1481

wants to merge 1 commit into from

Conversation

freiheit-kuberpult-upgrader
Copy link
Collaborator

@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader commented Mar 26, 2024

This PR contains the following updates:

Package Type Update Change
@azure/msal-browser dependencies minor 2.38.3 -> 2.39.0
@azure/msal-react dependencies patch 1.5.12 -> 1.5.13
@peculiar/webcrypto dependencies minor 1.4.5 -> 1.5.0
@testing-library/jest-dom devDependencies minor 6.4.0 -> 6.6.3
@testing-library/react devDependencies minor 16.0.1 -> 16.1.0
@types/node (source) devDependencies minor 20.11.10 -> 20.17.13
eslint (source) devDependencies minor 8.56.0 -> 8.57.1
eslint-plugin-no-only-tests (source) devDependencies minor 3.1.0 -> 3.3.0
eslint-plugin-prettier devDependencies minor 5.1.3 -> 5.2.1
google-protobuf devDependencies patch 3.21.2 -> 3.21.4
long devDependencies patch 5.2.3 -> 5.2.4
prettier (source) devDependencies minor 3.2.4 -> 3.4.2
protobufjs (source) devDependencies minor 7.2.6 -> 7.4.0
react-spinners (source) dependencies minor 0.13.8 -> 0.15.0
react-tooltip dependencies minor 5.26.0 -> 5.28.0
sass devDependencies minor 1.70.0 -> 1.83.4
ts-proto devDependencies minor 1.169.1 -> 1.181.2
typescript (source) devDependencies minor 5.4.3 -> 5.7.3

Release Notes

AzureAD/microsoft-authentication-library-for-js

v2.38.4

Compare Source

PeculiarVentures/webcrypto

v1.5.0

Compare Source

Features
1.4.6 (2024-03-29)
Bug Fixes
  • pass tag length for aes decipher (870ebef)
1.4.5 (2024-01-22)
1.4.4 (2024-01-16)
Bug Fixes
  • import Buffer before use (09d7d33)
  • use Buffer from 'buffer' (8b09641)
1.4.3 (2023-03-24)
Bug Fixes
  • type declaration for Crypto (335c2cb)
1.4.2 (2023-03-21)
Bug Fixes

v1.4.6

Compare Source

testing-library/jest-dom

v6.6.3

Compare Source

Bug Fixes
  • add vitest import when extending vitest matchers (#​646) (5ba0156)

v6.6.2

Compare Source

Bug Fixes

v6.6.1

Compare Source

Bug Fixes

v6.6.0

Compare Source

Features

v6.5.0

Compare Source

Features

v6.4.8

Compare Source

Bug Fixes

v6.4.7

Compare Source

Bug Fixes

v6.4.6

Compare Source

Bug Fixes

v6.4.5

Compare Source

Bug Fixes

v6.4.4

Compare Source

Bug Fixes

v6.4.3

Compare Source

Bug Fixes
  • Updates role support for aria-required attribute in toBeRequired (#​590) (20aca33)

v6.4.2

Compare Source

Bug Fixes
  • Remove errant export of GetByRoleMatcher, fixing type checking in some TS configurations (#​575) (a93c0c4)

v6.4.1

Compare Source

Bug Fixes
  • Export type TestingLibraryMatchers from "./matchers" (#​576) (dd1c4dd)
testing-library/react-testing-library

v16.1.0

Compare Source

Features
eslint/eslint

v8.57.1

Compare Source

Bug Fixes

  • a19072f fix: add logic to handle fixTypes in the lintText() method (#​18900) (Francesco Trotta)
  • 04c7188 fix: Don't lint same file multiple times (#​18899) (Francesco Trotta)
  • 87ec3c4 fix: do not throw when defining a global named __defineSetter__ (#​18898) (Francesco Trotta)
  • 60a1267 fix: Provide helpful error message for nullish configs (#​18889) (Milos Djermanovic)
  • a0dea8e fix: allow name in global ignores, fix --no-ignore for non-global (#​18875) (Milos Djermanovic)
  • 3836bb4 fix: do not crash on error in fs.walk filter (#​18886) (Milos Djermanovic)
  • 2dec349 fix: skip processor code blocks that match only universal patterns (#​18880) (Milos Djermanovic)

Documentation

Build Related

  • 35d366a build: Support updates to previous major versions (#​18870) (Milos Djermanovic)

Chores

v8.57.0

Compare Source

Features

  • 1120b9b feat: Add loadESLint() API method for v8 (#​18098) (Nicholas C. Zakas)
  • dca7d0f feat: Enable eslint.config.mjs and eslint.config.cjs (#​18066) (Nitin Kumar)

Bug Fixes

  • 2196d97 fix: handle absolute file paths in FlatRuleTester (#​18064) (Nitin Kumar)
  • 69dd1d1 fix: Ensure config keys are printed for config errors (#​18067) (Nitin Kumar)
  • 9852a31 fix: deep merge behavior in flat config (#​18065) (Nitin Kumar)
  • 4c7e9b0 fix: allow circular references in config (#​18056) (Milos Djermanovic)

Documentation

Chores

levibuzolic/eslint-plugin-no-only-tests

v3.3.0

Compare Source

What's Changed

Full Changelog: levibuzolic/eslint-plugin-no-only-tests@v3.2.0...v3.3.0

v3.2.0

Compare Source

What's Changed

Development Changes

New Contributors

Full Changelog: levibuzolic/eslint-plugin-no-only-tests@v3.1.0...v3.2.0

prettier/eslint-plugin-prettier

v5.2.1

Compare Source

Patch Changes
protocolbuffers/protobuf-javascript

v3.21.4

Compare Source

Release to fix bazel build layering issue in 3.21.3.

dcodeIO/long.js

v5.2.4

Compare Source

Bug fixes
  • Change source of truth for types to umd/index.d.ts to resolve issue with typescript import in 5.x (#​130) (d5ab8f6)
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

v3.3.3

Compare Source

diff

Add parentheses for nullish coalescing in ternary (#​16391 by @​cdignam-segment)

This change adds clarity to operator precedence.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);
Add parentheses for decorator expressions (#​16458 by @​y-schneider)

Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.

// Input
@&#8203;(foo`tagged template`)
class X {}

// Prettier 3.3.2
@&#8203;foo`tagged template`
class X {}

// Prettier 3.3.3
@&#8203;(foo`tagged template`)
class X {}
Support @let declaration syntax (#​16474 by @​sosukesuzuki)

Adds support for Angular v18 @let declaration syntax.

Please see the following code example. The @let declaration allows you to define local variables within the template:

@&#8203;let name = 'Frodo';

<h1>Dashboard for {{name}}</h1>
Hello, {{name}}

For more details, please refer to the excellent blog post by the Angular Team: Introducing @​let in Angular.

We also appreciate the Angular Team for kindly answering our questions to implement this feature.

v3.3.2

Compare Source

diff

Fix handlebars path expressions starts with @ (#​16358 by @​Princeyadav05)
{{! Input }}
<div>{{@&#8203;x.y.z}}</div>

{{! Prettier 3.3.1 }}
<div>{{@&#8203;x}}</div>

{{! Prettier 3.3.2 }}
<div>{{@&#8203;x.y.z}}</div>

v3.3.1

Compare Source

diff

Preserve empty lines in front matter (#​16347 by @​fisker)
<!-- Input -->
---
foo:
  - bar1

  - bar2

  - bar3
---
Markdown

<!-- Prettier 3.3.0 -->

---
foo:
  - bar1
  - bar2
  - bar3
---

Markdown

<!-- Prettier 3.3.1 -->
---
foo:
  - bar1

  - bar2

  - bar3
---

Markdown
Preserve explicit language in front matter (#​16348 by @​fisker)
<!-- Input -->
---yaml
title: Hello
slug: home
---

<!-- Prettier 3.3.0 -->
---
title: Hello
slug: home
---

<!-- Prettier 3.3.1 -->
---yaml
title: Hello
slug: home
---
Avoid line breaks in import attributes (#​16349 by @​fisker)
// Input
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

// Prettier 3.3.0
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type:
  "json" };

// Prettier 3.3.1
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

v3.3.0

Compare Source

diff

🔗 Release Notes

v3.2.5

Compare Source

diff

Support Angular inline styles as single template literal (#​15968 by @​sosukesuzuki)

Angular v17 supports single string inline styles.

// Input
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.4
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.5
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `
    h1 {
      color: blue;
    }
  `,
})
export class AppComponent {}
Unexpected embedded formatting for Angular template (#​15969 by @​JounQin)

Computed template should not be considered as Angular component template

// Input
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.4
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{ hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.5
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}
Use "json" parser for tsconfig.json by default (#​16012 by @​sosukesuzuki)

In v3.2.0, we introduced "jsonc" parser which adds trailing comma by default.

When adding a new parser we also define how it will be used based on the linguist-languages data.

tsconfig.json is a special file used by TypeScript, it uses .json file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing .json file extension.

We decide to treat it as a JSON file for now to avoid the extra configuration step.

To keep using the "jsonc" parser for your tsconfig.json files, add the following to your .prettierrc file

{
  "overrides": [
    {
      "files": ["tsconfig.json", "jsconfig.json"],
      "options": {
        "parser": "jsonc"
      }
    }
  ]
}
protobufjs/protobuf.js

v7.4.0

Compare Source

Features
  • Add prepublishOnly script (0e4da8b)
Bug Fixes

v7.3.3

Compare Source

Bug Fixes
  • handle nullability for optional fields (59569c1)

v7.3.2

Compare Source

Bug Fixes
  • docs: Update readme to correct command for creating types (#​1939) (0f9d477)

v7.3.1

Compare Source

Bug Fixes
  • types: reserved field in IType can contain reserved names (#​2001) (d1d2c0c)

v7.3.0

Compare Source

Features
davidhu2000/react-spinners

v0.15.0

Compare Source

What's Changed

New Contributors

Full Changelog: davidhu2000/react-spinners@0.14.1...v0.15.0

v0.14.1

Compare Source

  • revert #​602 due to issues with test and server side rendering

v0.14.0

Compare Source

  • feat: color prop can accept rgb colors #​586
  • fix: multiple hash loader with different color renders as the same color #​602
  • fix: moon loader wobble if size is not divisible by 7 #​603
ReactTooltip/react-tooltip

v5.28.0

Compare Source

If you like ReactTooltip, please give the project a star on GitHub 🌟

What's Changed

New Contributors

Full Changelog: ReactTooltip/react-tooltip@v5.27.1...v5.28.0

v5.27.1

Compare Source

If you like ReactTooltip, please give the project a star on GitHub 🌟

What's Changed

Full Changelog: ReactTooltip/react-tooltip@v5.27.0...v5.27.1

v5.27.0

Compare Source

If you like ReactTooltip, please give the project a star on GitHub 🌟

What's Changed

Full Changelog: ReactTooltip/react-tooltip@v5.26.4...v5.27.0

v5.26.4

Compare Source

If you like ReactTooltip, please give the project a star on GitHub 🌟

What's Changed

Full Changelog: ReactTooltip/react-tooltip@v5.26.3...v5.26.4

v5.26.3

Compare Source

If you like ReactTooltip, please give the project a star on GitHub 🌟

What's Changed

Full Changelog: ReactTooltip/react-tooltip@v5.26.2...v5.26.3

v5.26.2

Compare Source

If you like ReactTooltip, please give the project a star on GitHub 🌟

What's Changed

Full Changelog: ReactTooltip/react-tooltip@v5.26.1...v5.26.2

v5.26.1

Compare Source

If you like ReactTooltip, please give the project a star on GitHub 🌟

What's Changed

Full Changelog: ReactTooltip/react-tooltip@v5.26.0...v5.26.1

sass/dart-sass

v1.83.4

Compare Source

  • No user-visible changes.

v1.83.3

Compare Source

  • No user-visible changes.

v1.83.2

Compare Source

  • Properly display deprecation IDs for the JS Sass API.

  • Don't display deprecation IDs for user-defined deprecations.

v1.83.1

Compare Source

  • Fix a bug where --quiet-deps would get deactivated for @content blocks,
    even when those blocks were entirely contained within dependencies.

  • Include deprecation IDs in deprecation warnings to make it easier to determine
    what to pass to --silence-deprecation or --fatal-deprecation.

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: nu


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 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 has been generated by Renovate Bot.

@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader requested a review from a team as a code owner March 26, 2024 12:49
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader changed the title chore: update dependency ts-proto to ^1.170.0 fix: update npm Mar 27, 2024
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 7 times, most recently from 3d7a90a to 9ae3192 Compare April 6, 2024 01:03
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 4 times, most recently from e77685a to a4c0227 Compare April 14, 2024 01:04
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 4 times, most recently from e10b248 to 40af5e2 Compare April 22, 2024 12:50
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 7 times, most recently from 4f7d34b to 68d735b Compare May 1, 2024 01:04
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 4 times, most recently from 0ff8614 to 04c3ca1 Compare May 4, 2024 01:03
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 6 times, most recently from 3c165a5 to 6692862 Compare November 3, 2024 12:53
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 2 times, most recently from 21c33f3 to c7d2f83 Compare November 15, 2024 12:56
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 6 times, most recently from b1170fb to c710f44 Compare November 28, 2024 12:58
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 5 times, most recently from eb6cd35 to 37a8a0c Compare December 6, 2024 12:58
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 2 times, most recently from 40af18c to 59e863f Compare December 13, 2024 01:07
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 3 times, most recently from d008ce3 to 84228df Compare January 6, 2025 12:57
@freiheit-kuberpult-upgrader freiheit-kuberpult-upgrader force-pushed the renovate/npm branch 4 times, most recently from 6dadda4 to b518962 Compare January 14, 2025 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants