fix(deps): update external-major (major) #153

renovate · 2024-12-16T02:37:19Z

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Type	Update
@apollo/server (source)	`^4.12.2` -> `^5.2.0`	dependencies	major
@as-integrations/next	`^3.2.0` -> `^4.1.0`	dependencies	major
@biomejs/biome (source)	`^1.9.4` -> `^2.3.9`	devDependencies	major
@commitlint/cli (source)	`^19.8.1` -> `^20.2.0`	devDependencies	major
@commitlint/config-conventional (source)	`^19.8.1` -> `^20.2.0`	devDependencies	major
@prisma/client (source)	`^5.22.0` -> `^7.1.0`	dependencies	major
@types/node (source)	`^22.19.1` -> `^24.10.4`	devDependencies	major
@vitejs/plugin-react (source)	`^4.7.0` -> `^5.1.2`	devDependencies	major
actions/cache	`v4` -> `v5`	action	major
actions/checkout	`v4` -> `v6`	action	major
actions/setup-node	`v4` -> `v6`	action	major
dotenv	`^16.6.1` -> `^17.2.3`	devDependencies	major
eslint-plugin-react-hooks (source)	`^5.2.0` -> `^7.0.1`	devDependencies	major
globals	`^15.15.0` -> `^16.5.0`	devDependencies	major
is-ci	`^3.0.1` -> `^4.1.0`	devDependencies	major
jsdom	`^25.0.1` -> `^27.3.0`	devDependencies	major
lefthook	`^1.13.6` -> `^2.0.12`	devDependencies	major
magic-sdk (source)	`^28.21.1` -> `^32.0.0`	dependencies	major
prisma (source)	`^5.22.0` -> `^7.1.0`	devDependencies	major
tailwind-merge	`^2.6.0` -> `^3.4.0`	dependencies	major
tailwindcss (source)	`^3.4.18` -> `^4.1.18`	dependencies	major
vitest (source)	`^2.1.9` -> `^4.0.16`	devDependencies	major

Release Notes

apollographql/apollo-server (@apollo/server)

`v5.2.0`

Compare Source

Minor Changes

#8161 51acbeb Thanks @jerelmiller! - Fix an issue where some bundlers would fail to build because of the dynamic import for the optional peer dependency on @yaacovcr/transform introduced in @apollo/server 5.1.0. To provide support for the legacy incremental format, you must now provide the legacyExperimentalExecuteIncrementally option to the ApolloServer constructor.
```
import { legacyExecuteIncrementally } from '@&#8203;yaacovcr/transform';

const server = new ApolloServer({
  // ...
  legacyExperimentalExecuteIncrementally: legacyExecuteIncrementally,
});
```
If the legacyExperimentalExecuteIncrementally option is not provided and the client sends an Accept header with a value of multipart/mixed; deferSpec=20220824, an error is returned by the server.

`v5.1.0`

Compare Source

Minor Changes

#8148 80a1a1a Thanks @jerelmiller! - Apollo Server now supports the incremental delivery protocol (@defer and @stream) that ships with [email protected]. To use the current protocol, clients must send the Accept header with a value of multipart/mixed; incrementalSpec=v0.2.

Upgrading to 5.1 will depend on what version of graphql you have installed and whether you already support the incremental delivery protocol.

`v5.0.0`

Compare Source

BREAKING CHANGES

Apollo Server v5 has very few breaking API changes. It is a small upgrade focused largely on adjusting which versions of Node.js and Express are supported.

Read our migration guide for more details on how to update your app.

Dropped support for Node.js v14, v16, and v18, which are no longer under long-term support from the Node.js Foundation. Apollo Server 5 supports Node.js v20 and later; v24 is recommended. Ensure you are on a non-EOL version of Node.js before upgrading Apollo Server.
Dropped support for versions of the graphql library older than v16.11.0. (Apollo Server 4 supports graphql v16.6.0 or later.) Upgrade graphql before upgrading Apollo Server.
Express integration requires a separate package. In Apollo Server 4, you could import the Express 4 middleware from @apollo/server/express4, or you could import it from the separate package @as-integrations/express4. In Apollo Server 5, you must import it from the separate package. You can migrate your server to the new package before upgrading to Apollo Server 5. (You can also use @as-integrations/express5 for a middleware that works with Express 5.)
Usage Reporting, Schema Reporting, and Subscription Callback plugins now use the Node.js built-in fetch implementation for HTTP requests by default, instead of the node-fetch npm package. If your server uses an HTTP proxy to make HTTP requests, you need to configure it in a slightly different way. See the migration guide for details.
The server started with startStandaloneServer no longer uses Express. This is mostly invisible, but it does set slightly fewer headers. If you rely on the fact that this server is based on Express, you should explicitly use the Express middleware.
The experimental support for incremental delivery directives @defer and @stream (which requires using a pre-release version of graphql v17) now explicitly only works with version 17.0.0-alpha.2 of graphql. Note that this supports the same incremental delivery protocol implemented by Apollo Server 4, which is not the same protocol in the latest alpha version of graphql. As this support is experimental, we may switch over from "only alpha.2 is supported" to "only a newer alpha or final release is supported, with a different protocol" during the lifetime of Apollo Server 5.
Apollo Server is now compiled by the TypeScript compiler targeting the ES2023 standard rather than the ES2020 standard.
Apollo Server 5 responds to requests with variable coercion errors (eg, if a number is passed in the variables map for a variable declared in the operation as a String) with a 400 status code, indicating a client error. This is also the behavior of Apollo Server 3. Apollo Server 4 mistakenly responds to these requests with a 200 status code by default; we recommended the use of the status400ForVariableCoercionErrors: true option to restore the intended behavior. That option now defaults to true.
The unsafe precomputedNonce option to landing page plugins (which was only non-deprecated for 8 days) has been removed.

Patch Changes

There are a few other small changes in v5:

#8076 5b26558 Thanks @valters! - Fix some error logs to properly call logger.error or logger.warn with this set. This fixes errors or crashes from logger implementations that expect this to be set properly in their methods.
#7515 100233a Thanks @trevor-scheer! - ApolloServerPluginSubscriptionCallback now takes a fetcher argument, like the usage and schema reporting plugins. The default value is Node's built-in fetch.
Updated dependencies [100233a]:
- @apollo/server-gateway-interface@2.0.0

apollo-server-integrations/apollo-server-integration-next (@as-integrations/next)

`v4.1.0`

Compare Source

Minor Changes

#288 87f9e0f Thanks @martinnabhan! - Add support for Next.js 16

`v4.0.0`

Compare Source

Major Changes

#264 2572fca Thanks @karl-run! - Add support for Apollo Server 5

This release drops support for Apollo Server 4, and since Apollo Server 5 drops support for Node.js 18
we're also dropping support for Node.js 18.

biomejs/biome (@biomejs/biome)

`v2.3.9`

Compare Source

Patch Changes

#8232 84c9e08 Thanks @ruidosujeira! - Added the nursery rule noScriptUrl.

This rule disallows the use of javascript: URLs, which are considered a form of eval and can pose security risks such as XSS vulnerabilities.
```
<a href="javascript:alert('XSS')">Click me</a>
```
#8341 343dc4d Thanks @arendjr! - Added the nursery rule useAwaitThenable, which enforces that await is only used on Promise values.

Invalid

await "value";

const createValue = () => "value";
await createValue();

Caution

This is a first iteration of the rule, and does not yet detect generic "thenable" values.

#8034 e7e0f6c Thanks @Netail! - Added the nursery rule useRegexpExec. Enforce RegExp#exec over String#match if no global flag is provided.
#8137 d407efb Thanks @denbezrukov! - Reduced the internal memory used by the Biome formatter.
#8281 30b046f Thanks @tylersayshi! - Added the rule useRequiredScripts, which enforces presence of configurable entries in the scripts section of package.json files.

#8290 d74c8bd Thanks @dyc3! - The HTML formatter has been updated to match Prettier 3.7's behavior for handling <iframe>'s allow attribute.

- <iframe allow="layout-animations 'none'; unoptimized-images 'none'; oversized-images 'none'; sync-script 'none'; sync-xhr 'none'; unsized-media 'none';"></iframe>
+ <iframe
+ 	allow="
+ 		layout-animations 'none';
+ 		unoptimized-images 'none';
+ 		oversized-images 'none';
+ 		sync-script 'none';
+ 		sync-xhr 'none';
+ 		unsized-media 'none';
+ 	"
+ ></iframe>

#8302 d1d5014 Thanks @mlafeldt! - Fixed #8109: return statements in Astro frontmatter no longer trigger "Illegal return statement" errors when using experimentalFullSupportEnabled.
#8346 f3aee1a Thanks @arendjr! - Fixed #8292: Implement tracking
of types of TypeScript constructor parameter properties.

This resolves certain false negatives in noFloatingPromises and other typed
rules.

Example

class AsyncClass {
  async returnsPromise() {
    return "value";
  }
}

class ShouldBeReported {
  constructor(public field: AsyncClass) {}
  //          ^^^^^^^^^^^^----------------- Parameter property declaration

  async shouldBeReported() {
    // `noFloatingPromises` will now report the following usage:
    this.field.returnsPromise();
  }
}

#8326 153e3c6 Thanks @ematipico! - Improved the rule noBiomeFirstException. The rule can now inspect if extended configurations already contain the catch-all ** inside files.includes and, if so, the rule suggests removing ** from the user configuration.
#8433 397547a Thanks @dyc3! - Fixed #7920: The CSS parser, with Tailwind directives enabled, will no longer error when you use things like prefix(tw) in @import at rules.
#8378 cc2a62e Thanks @Bertie690! - Clarify diagnostic message for lint/style/useUnifiedTypeSignatures

The rule's diagnostic message now clearly states that multiple similar overload signatures are hard to read & maintain, as opposed to overload signatures in general.
#8296 9d3ef10 Thanks @dyc3! - biome rage now shows if you have experimental HTML full support enabled.
#8414 09acf2a Thanks @Bertie690! - Updated the documentation & diagnostic message for lint/nursery/noProto, mentioning the reasons for its longstanding deprecation and why more modern alternatives are preferred.

Notably, the rule clearly states that using __proto__ inside object literal definitions is still allowed, being a standard way to set the prototype of a newly created object.
#8445 c3df0e0 Thanks @tt-a1i! - Fix --changed and --staged flags throwing "No such file or directory" error when a file has been deleted or renamed in the working directory. The CLI now filters out files that no longer exist before processing.
#8459 b17d12b Thanks @ruidosujeira! - Fix #8435: resolved false positive in noUnusedVariables for generic type parameters in construct signature type members (new <T>(): T).
#8439 a78774b Thanks @tt-a1i! - Fixed #8011: useConsistentCurlyBraces no longer suggests removing curly braces from JSX expression children containing characters that would cause parsing issues or semantic changes when converted to plain JSX text ({, }, <, >, &).
#8436 a392c06 Thanks @ruidosujeira! - Fixed #8429. Formatter, linter, and assist settings now correctly inherit from global configuration when not explicitly specified in overrides.

Before this fix, when an override specified only one feature (e.g., only linter), other features would be incorrectly disabled instead of inheriting from global settings.

Example configuration that now works correctly:
```
{
  "formatter": { "enabled": true },
  "overrides": [
    {
      "includes": ["*.vue"],
      "linter": { "enabled": false }
    }
  ]
}
```
After this fix, .vue files will have the linter disabled (as specified in the override) but the formatter enabled (inherited from global settings).
#8411 9f1b3b0 Thanks @rriski! - Properly handle name, type_arguments, and attributes slots for JsxOpeningElement and JsxSelfClosingElement GritQL patterns.

The following biome search commands no longer throw errors:
```
biome search 'JsxOpeningElement(name = $elem_name) where { $elem_name <: "div" }'
biome search 'JsxSelfClosingElement(name = $elem_name) where { $elem_name <: "div" }'
```
#8441 cf37d0d Thanks @tt-a1i! - Fixed #6577: noUselessUndefined no longer reports () => undefined in arrow function expression bodies. Previously, the rule would flag this pattern and suggest replacing it with () => {}, which conflicts with the noEmptyBlockStatements rule.
#8444 8caa7a0 Thanks @tt-a1i! - Fix noUnknownMediaFeatureName false positive for prefers-reduced-transparency media feature. The feature name was misspelled as prefers-reduded-transparency in the keywords list.
#8443 c3fa5a1 Thanks @tt-a1i! - Fix useGenericFontNames false positive when a CSS variable is used as the last value in font-family or font. The rule now correctly ignores cases like font-family: "Noto Serif", var(--serif) and font: 1em Arial, var(--fallback).
#8281 30b046f Thanks @tylersayshi! - Fixed noDuplicateDependencies incorrectly triggering on files like _package.json.
#8315 c7915c4 Thanks @hirokiokada77! - Fixed #5213: The noDoneCallback rule no longer flags false positives when a method is called on a regular variable bound to identifiers such as before, after, beforeEach, and afterEach.
#8398 204844f Thanks @Bertie690! - The default value of the ignoreRestSiblings option for noUnusedVariables'
has been reverted to its prior value of true after an internal refactor accidentally changed it.

The diagnostic message has also been tweaked for readability.
#8242 9694e37 Thanks @dyc3! - Fixed bugs in the HTML parser so that it will flag invalid shorthand syntaxes instead of silently accepting them. For example, <Foo : foo="5" /> is now invalid because there is a space after the :.
#8297 efa694c Thanks @Yonom! - Added support for negative value utilities in useSortedClasses. Negative value utilities such as -ml-2 or -top-4 are now recognized and sorted correctly alongside their positive counterparts.
```
// Now detected as unsorted:
<div class="-ml-2 p-4 -mt-1" />
// Suggested fix:
<div class="-mt-1 -ml-2 p-4" />
```
#8335 3710702 Thanks @dibashthapa! - Added the new nursery rule useDestructuring. This rule helps to encourage destructuring from arrays and objects.

For example, the following code triggers because the variable name x matches the property foo.x, making it ideal for object destructuring syntax.
```
var x = foo.x;
```
#8383 59b2f9a Thanks @ematipico! - Fixed #7927: noExtraNonNullAssertion incorrectly flagged separate non-null assertions on both sides of an assignment.

The rule now correctly distinguishes between nested non-null assertions (still flagged) and separate non-null assertions on different sides of an assignment (allowed).

Examples

Valid (now allowed)

arr[0]! ^= arr[1]!;

Invalid (still flagged)

arr[0]!! ^= arr[1];
arr[0] ^= arr[1]!!;

#8401 382786b Thanks @Bertie690! - useExhaustiveDependencies now correctly validates custom hooks whose dependency arrays come before their callbacks.

Previously, a logical error caused the rule to be unable to detect dependency arrays placed before hook callbacks, producing spurious errors and blocking further diagnostics.

{
  "linter": {
    "rules": {
      "correctness": {
        "useExhaustiveDependencies": {
          "level": "error",
          "options": {
            "hooks": [
              {
                "name": "doSomething",
                "closureIndex": 2,
                "dependenciesIndex": 0
              }
            ]
          }
        }
      }
    }
  }
}

function component() {
  let thing = 5;
  // The rule will now correctly recognize `thing` as being specified
  // instead of erroring due to "missing" dependency arrays
  doSomething([thing], "blah", () => {
    console.log(thing);
  });
}

The rule documentation & diagnostic messages have also been reworked for improved clarity.

#8365 8f36051 Thanks @JacquesLeupin! - Fixed #8360: GritQL plugins defined in child configurations with extends: "//" now work correctly.
#8306 8de2774 Thanks @dibashthapa! - Fixed #8288: Fixed the issue with false positive errors

This new change will ignore attribute and only show diagnostics for JSX Expressions

For example

Valid:
```
<Something checked={isOpen && items.length} />
```
Invalid:
```
const Component = () => {
  return isOpen && items.length;
};
```
#8356 f9673fc Thanks @ematipico! - Fixed #7917, where Biome removed the styles contained in a <style lang="scss">, when experimentalFullSupportEnabled is enabled.
#8371 d71924e Thanks @ematipico! - Fixed #7343, where Biome failed to resolve extended configurations from parent directories using relative paths.
#8404 6a221f9 Thanks @fireairforce! - Fixed #7826, where a class member named async will not cause the parse error.
#8249 893e36c Thanks @cormacrelf! - Addressed #7538. Reduced the
volume of logging from the LSP server.

Use biome clean to remove large logs.

#8303 db2c65b Thanks @hirokiokada77! - Fixed #8300: noUnusedImports now detects JSDoc tags on object properties.

import type LinkOnObjectProperty from "mod";

const testLinkOnObjectProperty = {
	/**
	 * {@&#8203;link LinkOnObjectProperty}
	 */
	property: 0,
};

#8328 9cf2332 Thanks @Netail! - Corrected rule source reference. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#8403 c96dcf2 Thanks @dyc3! - Fixed #8340: noUnknownProperty will no longer flag anything in @plugin when the parser option tailwindDirectives is enabled
#8284 4976d1b Thanks @denbezrukov! - Improved the performance of the Biome Formatter by enabling the internal source maps only when needed.
#8260 a226b28 Thanks @ho991217! - Fixed biome-vscode#817: Biome now updates documents when the textDocument/didSave notification is received.
#8183 b064786 Thanks @hornta! - Fixed #8179: The useConsistentArrowReturn rule now correctly handles multiline expressions in its autofix when the style option is set to "always".

Previously, the autofix would incorrectly place a newline after the return keyword, causing unexpected behavior.

Example:
```
const foo = (l) => l.split("\n");
```
Now correctly autofixes to:
```
const foo = (l) => {
-   return
-   l.split('\n');
+   return l.split('\n');
}
```
#8382 7409cba Thanks @fireairforce! - Fixed #8338: Ignored the noUnknownTypeSelector check when the root selector is used under View Transition pseudo-elements.

Example
```
::view-transition-old(root),
::view-transition-new(root) {
  z-index: 1;
}
```
#7513 e039f3b Thanks @AsherDe! - Added the nursery rule noVueSetupPropsReactivityLoss.

This new rule disallows usages that cause the reactivity of props passed to the setup function to be lost.

Invalid code example:
```
export default {
  setup({ count }) {
    // `count` is no longer reactive here.
    return () => h("div", count);
  },
};
```

`v2.3.8`

Compare Source

Patch Changes

#8188 4ca088c Thanks @ematipico! - Fixed #7390, where Biome couldn't apply the correct configuration passed via --config-path.

If you have multiple root configuration files, running any command with --config-path will now apply the chosen configuration file.
#8171 79adaea Thanks @dibashthapa! - Added the new rule noLeakedRender. This rule helps prevent potential leaks when rendering components that use binary expressions or ternaries.

For example, the following code triggers the rule because the component would render 0:
```
const Component = () => {
  const count = 0;
  return <div>{count && <span>Count: {count}</span>}</div>;
};
```
#8116 b537918 Thanks @Netail! - Added the nursery rule noDuplicatedSpreadProps. Disallow JSX prop spreading the same identifier multiple times.

Invalid:
```
<div {...props} something="else" {...props} />
```
#8256 f1e4696 Thanks @cormacrelf! - Fixed a bug where logs were discarded (the kind from --log-level=info etc.). This is a regression introduced after an internal refactor that wasn't adequately tested.
#8226 3f19b52 Thanks @dyc3! - Fixed #8222: The HTML parser, with Vue directives enabled, can now parse v-slot shorthand syntax, e.g. <template #foo>.
#8007 182ecdc Thanks @brandonmcconnell! - Added support for dollar-sign-prefixed filenames in the useFilenamingConvention rule.

Biome now allows filenames starting with the dollar-sign (e.g. $postId.tsx) by default to support naming conventions used by frameworks such as TanStack Start for file-based-routing.
#8218 91484d1 Thanks @hirokiokada77! - Added the noMultiStr rule, which disallows creating multiline strings by escaping newlines.

Invalid:
```
const foo =
  "Line 1\n\
Line 2";
```
Valid:
```
const foo = "Line 1\nLine 2";
const bar = `Line 1
Line 2`;
```

#8225 98ca2ae Thanks @ongyuxing! - Fixed #7806: Prefer breaking after the assignment operator for conditional types with generic parameters to match Prettier.

-type True = unknown extends Type<
-  "many",
-  "generic",
-  "parameters",
-  "one",
-  "two",
-  "three"
->
-  ? true
-  : false;
+type True =
+  unknown extends Type<"many", "generic", "parameters", "one", "two", "three">
+    ? true
+    : false;

#6765 23f7855 Thanks @emilyinure! - Fixed #6569: Allow files to export from themselves with noImportCycles.

This means the following is now allowed:

// example.js
export function example() {
  return 1;
}

// Re-exports all named exports from the current module under a single namespace
// and then imports the namespace from the current module.
// Allows for encapsulating functions/variables into a namespace instead
// of using a static class.
export * as Example from "./example.js";

import { Example } from "./example.js";

#8214 68c052e Thanks @hirokiokada77! - Added the noEqualsToNull rule, which enforces the use of === and !== for comparison with null instead of == or !=.

Invalid:
```
foo == null;
foo != null;
```
Valid:
```
foo === null;
foo !== null;
```
#8219 793bb9a Thanks @dyc3! - Fixed #8190: The HTML parser will now parse Vue event handlers that contain : correctly, e.g. @update:modelValue="onUpdate".
#8259 4a9139b Thanks @hirokiokada77! - Fixed #8254: The noParameterAssign rule with propertyAssignment: "deny" was incorrectly reporting an error when a function parameter was used on the right-hand side of an assignment to a local variable's property.

The rule should only flag assignments that modify the parameter binding or its properties (L-value), not the use of its value.

Valid:
```
(input) => {
  const local = { property: 0 };
  local.property = input;
};
```
#8201 cd2edd7 Thanks @Netail! - Added the nursery rule noTernary. Disallow ternary operators.

Invalid:
```
const foo = isBar ? baz : qux;
```
#8172 de98933 Thanks @JeremyMoeglich! - Fixed #8145: handling of large hex literals, which previously caused both false positives and false negatives.

This affects noPrecisionLoss and noConstantMathMinMaxClamp.
#8210 7b44e9e Thanks @Netail! - Corrected rule source reference. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#8213 e430555 Thanks @ruidosujeira! - Fixed #8209: Recognized formatting capability when either range or on-type formatting is supported, not only full-file formatting. This ensures editors and the language server correctly detect formatting support in files like JSONC.
#8202 6f49d95 Thanks @hirokiokada77! - Fixed #8079: Properly handle name and value metavariables for JsxAttribute GritQL queries.

The following biome search command no longer throws an error:
```
biome search 'JsxAttribute($name, $value) as $attr where { $name <: "style" }'
```
#8276 f7e836f Thanks @hirokiokada77! - Added the noProto rule, which disallows the use of the __proto__ property for getting or setting the prototype of an object.

Invalid:
```
obj.__proto__ = a;
const b = obj.__proto__;
```
Valid:
```
const a = Object.getPrototypeOf(obj);
Object.setPrototypeOf(obj, b);
```

`v2.3.7`

Compare Source

Patch Changes

#8169 7fdcec8 Thanks @arendjr! - Fixed #7999: Correctly place await after leading comment in auto-fix action from noFloatingPromises rule.
#8157 12d5b42 Thanks @Conaclos! - Fixed #8148. noInvalidUseBeforeDeclaration no longer reports some valid use before declarations.

The following code is no longer reported as invalid:
```
class classA {
  C = C;
}
const C = 0;
```
#8178 6ba4157 Thanks @dyc3! - Fixed #8174, where the HTML parser would parse 2 directives as a single directive because it would not reject whitespace in Vue directives. This would cause the formatter to erroneously merge the 2 directives into one, resulting in broken code.
```
- <Component v-else:property="123" />
+ <Component v-else :property="123" />
```
#8088 0eb08e8 Thanks @db295! - Fixed #7876: The noUnusedImports rule now ignores imports that are used by @linkcode and @linkplain (previously supported @link and @see).

The following code will no longer be a false positive:
```
import type { a } from "a"

/**
 * {@&#8203;linkcode a}
 */
function func() {}
```
#8119 8d64655 Thanks @ematipico! - Improved the detection of the rule noUnnecessaryConditions. Now the rule isn't triggered for variables that are mutated inside a module.

This logic deviates from the original rule, hence noUnnecessaryConditions is now marked as "inspired".

In the following example, hey starts as false, but then it's assigned to a string. The rule isn't triggered inside the if check.
```
let hey = false;

function test() {
  hey = "string";
}

if (hey) {
}
```
#8149 e0a02bf Thanks @Netail! - Fixed #8144: Improve noSyncScripts, ignore script tags with type="module" as these are always non-blocking.
#8182 e9f068e Thanks @hirokiokada77! -

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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 was generated by Mend Renovate. View the repository job log.

deepsource-io · 2024-12-16T02:37:41Z

Here's the code health analysis summary for commits 0171653..7a43204. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

renovate bot added the dependencies label Dec 16, 2024

renovate bot assigned ChiefORZ Dec 16, 2024

renovate bot force-pushed the renovate/major-external-major branch 4 times, most recently from c2033ad to 29c8dca Compare December 23, 2024 04:45

renovate bot force-pushed the renovate/major-external-major branch from 29c8dca to 3287226 Compare December 30, 2024 04:05

renovate bot force-pushed the renovate/major-external-major branch 7 times, most recently from 98a5b5e to 2c31797 Compare January 13, 2025 01:11

renovate bot force-pushed the renovate/major-external-major branch 6 times, most recently from 340629c to 67037b6 Compare January 20, 2025 05:40

renovate bot force-pushed the renovate/major-external-major branch 5 times, most recently from 045a25a to 02b8067 Compare January 28, 2025 17:12

renovate bot force-pushed the renovate/major-external-major branch 4 times, most recently from 30ec0e1 to 5d36c6d Compare January 31, 2025 20:40

renovate bot force-pushed the renovate/major-external-major branch 6 times, most recently from 9e23630 to 3c28d38 Compare November 25, 2025 17:01

renovate bot force-pushed the renovate/major-external-major branch 7 times, most recently from c80b4b7 to 78380a0 Compare December 3, 2025 18:34

renovate bot force-pushed the renovate/major-external-major branch 9 times, most recently from 147f2ce to 9bf2124 Compare December 12, 2025 02:36

renovate bot force-pushed the renovate/major-external-major branch 6 times, most recently from d08f08d to 2fcfae6 Compare December 15, 2025 17:54

fix(deps): update external-major

7a43204

renovate bot force-pushed the renovate/major-external-major branch from 2fcfae6 to 7a43204 Compare December 16, 2025 18:10

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update external-major (major) #153

fix(deps): update external-major (major) #153

Uh oh!

renovate bot commented Dec 16, 2024 •

edited

Loading

Uh oh!

deepsource-io bot commented Dec 16, 2024 •

edited

Loading

Analysis Summary

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

fix(deps): update external-major (major) #153

Are you sure you want to change the base?

fix(deps): update external-major (major) #153

Uh oh!

Conversation

renovate bot commented Dec 16, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Minor Changes

Minor Changes

BREAKING CHANGES

Patch Changes

Minor Changes

Major Changes

Patch Changes

Invalid

Caution

Example

Examples

Valid (now allowed)

Invalid (still flagged)

Patch Changes

Patch Changes

Configuration

Uh oh!

deepsource-io bot commented Dec 16, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Analysis Summary

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

renovate bot commented Dec 16, 2024 •

edited

Loading

deepsource-io bot commented Dec 16, 2024 •

edited

Loading