RENOVATE: Update all non-major dependencies by renovate[bot] · Pull Request #214 · adobe/commerce-integration-starter-kit

renovate · 2026-11-02T03:00:40Z

This PR contains the following updates:

Package	Change	Type	Update
@biomejs/biome (source)	`2.6.3` → `2.6.4`	devDependencies	patch
@biomejs/biome (source)	`2.6.3` → `2.6.4`		patch
cloudflare/cloudflared	`2026.10.5` → `2026.10.7`		patch
grafana/otel-lgtm	`0.38.1` → `0.39.0`		minor

Release Notes

biomejs/biome (@biomejs/biome)

`v2.6.4`

Compare Source

Patch Changes

#12261 19fbfb2 Thanks @dyc3! - Added the new nursery rule noConsoleSpaces, which reports a leading or trailing space in a console.log(), console.debug(), console.info(), console.warn(), or console.error() argument that sits next to another argument. These methods already put a space between arguments, so such a space prints twice.
```
console.log("abc ", "def");
```
#12469 cd716d3 Thanks @dyc3! - Added the new nursery rule noMagicArrayFlatDepth, which reports number literals other than 1 passed as the depth of Array.prototype.flat() unless a comment inside the parentheses explains them.
```
const items = array.flat(2);
```
#12470 92c9e81 Thanks @dyc3! - Added the nursery rule noNull, which reports uses of the null literal and suggests undefined instead. Strict comparisons such as foo === null are allowed.
```
let foo = null;
```
#12483 9bd3527 Thanks @dyc3! - Added the nursery rule noReturnArrayPush, which reports code that uses the return value of push() or unshift(). These methods return the new length of the array, not the added item or the array.
```
function add(item) {
  return items.push(item);
}
```
#12477 a384892 Thanks @dyc3! - Added the nursery rule noUnreadableIife, which reports arrow functions that are called right where they are defined and whose body is wrapped in parentheses.
```
const foo = (bar => (bar ? bar.baz : baz))(getBar());
```
#12447 0a963e4 Thanks @dyc3! - Added the nursery rule noUselessRecursion, which reports functions that return a call to themselves when a loop can do the same work. Too many nested calls can crash the program with a stack overflow error.
```
function findRoot(node) {
    if (node.parent) {
        return findRoot(node.parent);
    }
    return node;
}
```
#12554 2eddda9 Thanks @dyc3! - Added the nursery rule noVueComputedPropertiesInData, which reports computed properties used inside the data function of a Vue component. Vue runs data before it sets up computed properties, so the value read there is undefined.
```
<script>
export default {
  data() {
    return { total: this.doubled };
  },
  computed: {
    doubled() {
      return 2;
    },
  },
};
</script>
```
#12586 824df15 Thanks @dyc3! - Added the nursery rule noVueDeprecatedDeleteSet, which reports calls to the $set and $delete functions, Vue.set and Vue.delete, and set and del imported from vue. Vue 3 removed these functions, so calling them throws an error.
```
<script>
export default {
  mounted() {
    this.$set(this.user, "name", "Alice");
  },
};
</script>
```
#12648 6fc1a51 Thanks @dyc3! - Added the nursery rule noVueDeprecatedRouterLinkTagProp, which disallows the tag prop on RouterLink. Vue Router 4 ignores this prop, so the link still renders as an <a> element.
```
<template>
  <RouterLink tag="li" to="/">Home</RouterLink>
</template>
```
#12631 de1188f Thanks @dyc3! - Added the new nursery rule noVueDeprecatedScopeAttribute, which reports the scope attribute on <template> elements in Vue files. Vue no longer supports this attribute, so use v-slot to receive slot props instead.
```
<template>
  <ListComponent>
    <template scope="props">{{ props.title }}</template>
  </ListComponent>
</template>
```
#12562 5d7553b Thanks @dyc3! - Added the new nursery rule noVueMultipleSlotArgs, which disallows passing more than one argument to a Vue slot from a render function. Slot content written in a template receives only the first argument.
```
<script>
export default {
  render() {
    return this.$slots.default(item, index); // reported
  },
};
</script>
```
#12513 2e520d8 Thanks @dyc3! - Added the nursery rule noVueMutatingProps, which reports code that changes the props of a Vue component, in the script or in the template. Props belong to the parent component, so the child should emit an event or copy the value instead.
```
<script setup>
const props = defineProps({ items: Array });

props.items.push("new item");
</script>
```
#12567 144b786 Thanks @dyc3! - Added the nursery rule noVueSideEffectsInComputed, which reports Vue computed properties that change state. Vue decides when to run a computed property, so changes made inside one happen at unpredictable times.
```
<script setup>
import { computed, ref } from "vue";

const items = ref([]);
// `reverse()` changes `items.value` in place.
const reversedItems = computed(() => items.value.reverse());
</script>
```
#12603 861b288 Thanks @dyc3! - Added the new nursery rule noVueUnusedRefs, which reports template refs in Vue components that nothing reads through $refs, useTemplateRef(), or a variable of the same name in <script setup>. The rule needs html.experimentalFullSupportEnabled to be true.
```
<template>
  <input ref="input" />
</template>
```
#12285 68770e0 Thanks @dyc3! - Added the new nursery rule noYamlBooleanKeys, which disallows boolean values as keys in YAML. For example, the following key is a boolean instead of text, so it is reported:
```
true: enabled
```
#12338 f46411b Thanks @dyc3! - Added the nursery rule useSvelteEventDispatcherTypes, which reports createEventDispatcher() calls that don't declare the types of their events in Svelte components written in TypeScript.

The rule accepts a call that declares its events:
```
<script lang="ts">
  import { createEventDispatcher } from "svelte";

  const dispatch = createEventDispatcher<{ save: string }>();
</script>
```
#12615 ade9845 Thanks @dyc3! - Added the nursery rule useVueDefineOptions, which reports the default export of a plain <script> block in Vue components that also use <script setup>, and suggests setting those options with defineOptions() instead.
```
<script>
export default { name: "MyComponent" }; // reported
</script>

<script setup>
const props = defineProps(["title"]);
</script>
```
#12514 e74b4dc Thanks @dyc3! - Added the nursery rule useVueDefinePropsDestructuring, which requires destructuring the props returned by defineProps() in Vue <script setup> blocks. It also reports withDefaults(), because destructured props can set their default values directly.
```
<script setup lang="ts">
const props = defineProps<{ foo?: string }>();
</script>
```
#12559 94985ba Thanks @dyc3! - Added the nursery rule useVueTemplateRef, which requires useTemplateRef() instead of ref() or shallowRef() to access elements of the template in <script setup>.
```
<template>
  <input ref="input" />
</template>

<script setup>
import { ref } from "vue";

const input = ref(); // reported
</script>
```
#12512 6be5078 Thanks @dyc3! - Added the nursery rule useVueTypedProps, which reports Vue props declared without a type, in the props option, defineProps(), or defineModel(). Without a type, Vue accepts any value for the prop and can't warn when a component receives the wrong kind of value.
```
<script setup>
defineProps(["title"]);
</script>
```
#12653 f307633 Thanks @dyc3! - Added the nursery rule useVueVModel, which reports a prop binding on a Vue component paired with an update: listener that only writes the new value back, and suggests v-model instead.
```
<template>
  <MyComponent :title="title" @update:title="title = $event" />
</template>
```
#12591 a810209 Thanks @dyc3! - Added the nursery rule useVueValidDefineEmits, which enforces valid usage of Vue's defineEmits macro in <script setup>.

For example, the following code is now reported, because defineEmits declares its events with both a type and an argument:
```
<script setup lang="ts">
const emit = defineEmits<(e: "notify") => void>(["submit"]);
</script>
```
#12614 9308110 Thanks @dyc3! - Added the nursery rule useVueValidDefineProps, which reports defineProps() calls that Vue can't compile or that declare props incorrectly. For example, it reports a component that calls defineProps() twice, or whose defineProps() argument uses a variable declared in <script setup>:
```
<script setup>
const definition = { msg: String };
defineProps(definition);
</script>
```
#12570 222a230 Thanks @dyc3! - Added the nursery rule useVueValidVIs, which reports v-is directives that have an argument or modifiers, have no value, or are used on a component instead of a native HTML element.

For example, the following v-is directive has no value:
```
<template>
  <tr v-is></tr>
</template>
```
#12521 4010bb7 Thanks @dyc3! - Added the nursery rule useVueValidVMemo, which reports invalid v-memo directives in Vue templates. A v-memo directive must have an array value, can't have an argument or modifiers, and doesn't work inside an element with v-for.

For example, the following value is an object instead of an array:
```
<template>
  <div v-memo="{ id }"></div>
</template>
```
#12597 aff42a7 Thanks @dyc3! - Added the nursery rule useVueValidVModel, which reports v-model directives that Vue can't use: on unsupported elements or file inputs, with an argument or unknown modifier on a native element, without a value, or with a value that can't be assigned to.

For example, the following v-model directives are invalid:
```
<template>
  <div v-model="foo"></div>
  <input v-model="foo + bar" />
</template>
```
#12569 3058597 Thanks @dyc3! - Added the new nursery rule useVueValidVShow, which reports v-show directives that have an argument, a modifier, or no value, or that are placed on a <template> element.
```
<template v-show="isVisible"><div></div></template>
```
#12525 e2e5a36 Thanks @dyc3! - Added the nursery rule useVueValidVSlot, which reports misplaced, duplicated, or malformed v-slot directives in Vue templates.

For example, the rule reports two <template> elements that fill the same slot:
```
<MyComponent>
  <template #header>First title</template>
  <template #header>Second title</template>
</MyComponent>
```
#12472 efd16bd Thanks @dyc3! - Added the new nursery rule useWhileLoopCondition, which reports loops such as while (true) and for (;;) that start with an if statement containing only a break, and moves that condition into the while statement.
```
while (true) {
  if (!hasMore()) {
    break;
  } // reported
  processNext();
}
```
#12640 167bb00 Thanks @latin-1! - Updated useSortedProperties to follow stylelint-config-recess-order 7.9.0, adding sorting support for scroll-behavior, anchor positioning, multi-column layout, and other properties known to Biome.
#12719 40a82b0 Thanks @dyc3! - Improved the performance of the linter. Biome now spends less time setting up the enabled rules for each file it analyzes.
#12722 f074730 Thanks @dyc3! - Improved the performance of biome lint by about 1% to 3% on large projects, most noticeably with Biome's default rules and with rules that track variables or unreachable code.
#12501 90a4d74 Thanks @ematipico! - Fixed #12466: the Biome daemon used more memory with every biome check --use-server run. The daemon now reuses the data that it stores for each file and project, and it keeps syntax trees only for the files that it read most recently.
#12501 90a4d74 Thanks @ematipico! - Fixed biomejs/biome-vscode#923: when a file open in the editor changed on disk, the language server replaced the editor's text with the text on disk. Biome now keeps the editor's text of open files until they are closed, so diagnostics, code actions and formatting stay at the right positions.

#12652 59ff42a Thanks @kurovskyiii! - Fixed #12651: an imported name that the other module exports as both a type and a value now resolves to the type in type annotations, so noBaseToString no longer reports slug below as an object.

// rule-slug.ts
export type RuleSlug = string;
export const RuleSlug = { create: (text: string): RuleSlug => text } as const;

// main.ts
import { RuleSlug } from "./rule-slug";
export const label = (slug: RuleSlug): string => `rule ${slug}`;

#12678 301402f Thanks @nhedger! - Fixed biomejs/biome-vscode#1113: the language server now shows a warning when the configuration file can't be parsed. Previously, Biome stopped processing files without telling the user why.
#12662 8c836eb Thanks @dyc3! - Fixed #12645: the Markdown formatter no longer removes the blank line between a blockquote and the list that follows it, matching Prettier.
```
> A note.

- one
- two
```
#12662 8c836eb Thanks @dyc3! - Fixed #12663: the Markdown formatter no longer removes the blank line between a table and the list that follows it, matching Prettier.
```
| Table |
| ----- |
| Value |

- Hello
```
#12576 735d370 Thanks @jfmcdowell! - Fixed #12541: Markdown list items whose markers are indented 4 or more spaces now nest at the correct level. Previously the formatter could move such an item under the item before it, or join it to that item's text.
```
 1. Step
    - a
      - x
-       - y
-         - b
+     - y
+   - b
```
#12575 0da9080 Thanks @jfmcdowell! - Fixed formatting of Markdown block quotes inside deeply indented list items. With proseWrap: "always", consecutive quote lines now wrap together within the same quote, while setext headings and fenced code blocks keep their structure.
```
 10. item
-    > first line
-    > second line
+    > first line second line
```

#12607 896d53e Thanks @xucian! - Fixed #12542: the Markdown formatter is now idempotent when it formats tables.

- | a        | b     |
- | -------- | ----- |
- | x        | `y` z |
- | `p` z`q` | r     |
+ | a         | b     |
+ | --------- | ----- |
+ | x         | `y` z |
+ | `p` z `q` | r     |

#12692 8ff63f4 Thanks @NikitaCOEUR! - Fixed the linux-x64-musl binary not using jemalloc, which it already ships: it fell back to musl's allocator, and biome check on several threads could take minutes instead of seconds, for example in Alpine-based CI images.
#12682 fa7cf4c Thanks @dyc3! - Fixed #12679: when markdown.parser.frontmatter and markdown.formatter.formatEmbeds are enabled, the Markdown formatter keeps the frontmatter of a fenced Markdown code block as written. Previously, it formatted the frontmatter as a thematic break and a paragraph, which removed the indentation of its YAML.
```
```markdown
---
verified:
  by: human
---
```

Policy

#12649 343c8ca Thanks @JamBalaya56562! - Fixed #12643 and #12669: Biome now migrates the Prettier option bracketSpacing to formatter.bracketSpacing, both at the top level and inside overrides. JSON and GraphQL files are now formatted with the same bracket spacing as JavaScript files.
#12640 167bb00 Thanks @latin-1! - Fixed useSortedProperties to withhold sorting fixes that would change the effective values of overlapping declarations, physical/logical border or corner properties, or declarations followed by all.
Updated noShorthandPropertyOverrides to recognize logical border, corner shape, position-try, text-box, and transition-behavior overrides.
#12723 b6cbec8 Thanks @dyc3! - Improved the performance of biome lint, biome check, and biome ci on files where rules report diagnostics with code fixes, by up to 12% with the default rules.
#12664 6021da0 Thanks @MindTooth! - Fixed Biome processing pnpm-lock.yaml files. These generated lockfiles are now protected from processing.
#12501 90a4d74 Thanks @ematipico! - Fixed an issue where the CLI, when it ran with --use-server alongside an editor connected to the same daemon, checked the unsaved text of the files open in the editor instead of the files on disk, and could make the editor's text get lost. The CLI now checks the files on disk, and every editor and CLI run connected to the daemon keeps its own text of the files it opens.
#12519 9ae56ba Thanks @dyc3! - The rule noVueVIfWithVFor now also reports v-else-if and v-else on the same element as v-for.
```
<div v-if="loading">Loading...</div>
<TodoItem v-else v-for="todo in todos" :todo="todo" />
```
#12702 df0f7cc Thanks @dyc3! - Fixed parsing of default values in Vue v-for bindings. Biome now parses the default value as JavaScript, so it is formatted and linted like other template expressions instead of being reported as a parse error.
```
<div v-for="{ value = gt('v-for default') } in rows" />
```
#12656 25a00a2 Thanks @dyc3! - Fixed non-JSON files inside the global settings directories of Zed, VS Code, and Cursor being parsed as JSON.
#12501 90a4d74 Thanks @ematipico! - Fixed an issue where the language server kept using the previous parser options for open files after the configuration changed. Open files are now parsed again with the new options, for example json.parser.allowComments.
#12656 25a00a2 Thanks @dyc3! - Improved the performance of Biome when it processes many files by up to 7%.
#12661 066a077 Thanks @dyc3! - Added the nursery rule noVueDeprecatedListeners. It reports references to $listeners, which Vue 3 removed, in Vue templates and component objects. For example, Biome now reports <div v-on="$listeners" /> and this.$listeners inside a Vue component.

cloudflare/cloudflared

`v2026.10.7`

Compare Source

SHA256 Checksums:

cloudflared-amd64.pkg: 917e804561007221f83d9ba2ebd3dc9f7f2f328653d52af33e91e4a7a942d1fb
cloudflared-arm64.pkg: 1ec2fdf94235f0b1422296383cb3eb028b75f4d9c2f2d51255651a3da2e357e6
cloudflared-darwin-amd64.tgz: 5c55e77da7012cebca19170357e196176c48c9647cc2ead404702fa125ddbd86
cloudflared-darwin-arm64.tgz: 2136431d5eb467bf447d2ee514b713e192719b143aec1d9e09bf7dc290d5bb12
cloudflared-fips-linux-amd64: 426c7c0e3bdb1b62f43b88ede364c7e41bee9b5a5397546d1dd301420c75f9c7
cloudflared-fips-linux-amd64.deb: 5ecda786849ef40b73407fcf946e922224a587f53ca4394745f521b567bb0c8c
cloudflared-fips-linux-x86_64.rpm: 796608193f67341a37d86fec6097da8d439149593de8150df923495878dff0b7
cloudflared-linux-386: 4823d2f038395617e04e4070601ab45c0c43f31f15ee7586be299e19ef49d46e
cloudflared-linux-386.deb: 3b8c98b929855469a1bed892b4a2c5a88b25b071bb3307e670cf55cff10c0880
cloudflared-linux-386.rpm: 155f7152eb85700569ae09c638b7088532ea9e66031ec10d272feb052509ffe3
cloudflared-linux-aarch64.rpm: 6e58e8e388a4b4454b0f6c80f00eecbc98ac40a9bed76c4afc261b6ca7300c04
cloudflared-linux-amd64: 1f99fb518b83dec2ba8d870a7cc991d82a77e6196295a3d2754ba17ab9f91872
cloudflared-linux-amd64.deb: 70b1a1e0f46033ffc8d90b406e554044ba6cbf2e4360295ef1163aed31e09393
cloudflared-linux-arm: 74f690f6707182839b63e0465726c7776dd63f0a174390b911d5d71f35cab94e
cloudflared-linux-arm.deb: d8ad068223c19b9221319e7985c6ed0423f11e472493228a344ed347b0f1c93f
cloudflared-linux-arm.rpm: f6f20852c7269a2c83635bad6a93ea8f4015356c4711318b1709a330f95409dc
cloudflared-linux-arm64: 3df43aedc9ff291d1735b5cb576cb97e0b157488796db2e32b28aecabb445775
cloudflared-linux-arm64.deb: d9407eb6e70ac31f54978a6b408a0320b51b664a6d0b498248692d7ac56bf836
cloudflared-linux-armhf: 04548d1d5e6a45eaec43916078538192e447256bcc3551bc8265c4ece06a655b
cloudflared-linux-armhf.deb: a89914a3db4faeaf935d673ccc5ca549655ebb2bb9b5db1ef23389ff51358216
cloudflared-linux-armhf.rpm: 5622d077583cb93f86b45a0182c144b36615464f60ad6191ebbb39f77d5ce5cc
cloudflared-linux-x86_64.rpm: 26c47d9d361459a818b519bc6b207dafe941bc50da921294752c6b0f094c32f0
cloudflared-windows-386.exe: 88c6b972b410db0e26745f593510d772c825a13c5a2374819e3f13a05b333082
cloudflared-windows-386.msi: d083222b52b52d73b477a922fe7bfb0043d7fca77228edd5ac155bab1c9dbe6f
cloudflared-windows-amd64.exe: 2493dbc168923bb3e59e5e7716f71deced92992eea9acd6e9d74f84ac7751343
cloudflared-windows-amd64.msi: 057a1370fe26b1a4d45d8673c219fa3ddb3c3b4bcbf0cde25ee938c932645387

`v2026.10.6`

Compare Source

SHA256 Checksums:

cloudflared-amd64.pkg: dd58d7ab72eb821ba54282fcabf659edbf197a9f10e1f8a9ceb00a48aeb1fc31
cloudflared-arm64.pkg: 591501ceb3ae7db9277b9a6dd5709984ea55823c7e305fac6fae703b85bb0f24
cloudflared-darwin-amd64.tgz: 2b74a9a6b9e5161dbf79a77c2fcc6337cd7e9d2b23eee9d1b6635ecb17608589
cloudflared-darwin-arm64.tgz: 380451015c3676789adc4200f43757e950e7173b920b0094e272e8bea59d7927
cloudflared-fips-linux-amd64: 130f1104dfb502378e875e69137d72f8e758fab5268d04e9f6df9af01279f454
cloudflared-fips-linux-amd64.deb: a8118cf0b6122b7713f8fb4dab22dbca444bcfbbe251db3fd45414c6a5ee539b
cloudflared-fips-linux-x86_64.rpm: 4d35b285bdba6310ac7b718e75051300a21ca338c2874a8560d5b0d1420d3bcf
cloudflared-linux-386: 2d2b419cd3d68611774364a6d04246a1ad8c4529186f6f3bcf40b25ab150cab4
cloudflared-linux-386.deb: 6ca05ccf8a2132377fee8e181226fdf5a6afe3b55f9719d1ed1cfab3138df6ba
cloudflared-linux-386.rpm: faa4f0bad6ec8c0b9ff44bec444fe58f51a186a80596471aba418d271af26188
cloudflared-linux-aarch64.rpm: 2b1aa3ee65a41d799b418c7d677fc710c7f3e60fd173d905f601a4d8766da630
cloudflared-linux-amd64: 1d356dac769d0dbf62ebe588c4034824bbff98d5790c2f844cc99e0e2f57462d
cloudflared-linux-amd64.deb: 13d9a724a4d4271958a3728982ee983870a100959a159d2fa263b3450d0be72a
cloudflared-linux-arm: 276b306200086dee90c10954fa37cf26a6664052fa750e04b1831f69158cd2f6
cloudflared-linux-arm.deb: 45b8e1da3ca9ab0728df863d963526bd478e040b615d63620bbeac3ad718f24f
cloudflared-linux-arm.rpm: 5ca4f2f9497bc24055d2892bee4a96474a4c1a7d7f98d535daabfe04ec6089d2
cloudflared-linux-arm64: 0ae0e179475b2c77651a718d2b376e0151f4fca5954702a84f02843a4d5fcac0
cloudflared-linux-arm64.deb: 621cd69e4c01c04813d74f446ccdd7eead7808dd9f6bfe0d15f7126d15a75792
cloudflared-linux-armhf: 2d1e01655e12c82cb038dd662fa7cd567623f5fe995db1e09a968b5d091fb752
cloudflared-linux-armhf.deb: 11d02b0e4664b2e2be4171969ddd1d5a2143ad42c5dccdf0353fca46d0be81c1
cloudflared-linux-armhf.rpm: 9cb3439efef77606bea9c47ffff24a2b524d0333f0d11daa2fe77680bb18ef0b
cloudflared-linux-x86_64.rpm: f05abc1e873c10aa18f4e3c0d01369662f233a668e2c2ef353b15c4bb7a747bb
cloudflared-windows-386.exe: 617379457c8e91a3090c7ce48017ae623571ce53e8eae668972d11158a530091
cloudflared-windows-386.msi: ce4579b34977414e5ddff1c77181586317a913952c08f575de33eaaf6ff4eb47
cloudflared-windows-amd64.exe: d521b3bf68982165f0d06d76732f22d9a105ef057ff3ae4c0986f3a23190950f
cloudflared-windows-amd64.msi: f702616fceb9a4500b2a1e7d894c8a3833f5ed6c420ec0c467629b037b44f41c

grafana/docker-otel-lgtm (grafana/otel-lgtm)

`v0.39.0`

Compare Source

What's Changed

OpenTelemetry & LGTM

chore(deps): update dependency opentelemetry-collector to v0.164.0 by @renovate-sh-app[bot] in #2052
chore(deps): update dependency grafana to v13.3.0 by @renovate-sh-app[bot] in #2051
chore(deps): update grafana/otel-lgtm docker tag to v0.38.1 by @renovate-sh-app[bot] in #2057
chore(deps): update dependency pyroscope to v2.4.2 by @renovate-sh-app[bot] in #2056

Other Changes

Support running as an arbitrary UID by @edeandrea in #2038
chore(deps): bump Flint to v0.22.15 by @zeitlinger in #2053

New Contributors

@edeandrea made their first contribution in #2038

Full Changelog: grafana/docker-otel-lgtm@v0.38.1...v0.39.0

Configuration

📅 Schedule: (UTC)

Branch creation
- "on Monday"
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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: Update all non-major dependencies

60aef6c

renovate Bot added the dependencies Pull requests that update a dependency file label Nov 2, 2026

renovate Bot requested a review from a team as a code owner November 2, 2026 03:00

renovate Bot added the dependencies Pull requests that update a dependency file label Nov 2, 2026

renovate-approve Bot approved these changes Nov 2, 2026

View reviewed changes

renovate Bot merged commit be9eda6 into main Nov 2, 2026
4 checks passed

renovate Bot deleted the renovate/all-non-major branch November 2, 2026 06:44

Navigation Menu

Repository navigation

RENOVATE: Update all non-major dependencies - #214

RENOVATE: Update all non-major dependencies#214
renovate[bot] merged 1 commit into
mainfrom
renovate/all-non-major

renovate Bot commented Nov 2, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Nov 2, 2026

Release Notes

v2.6.4

Patch Changes

Policy

v2026.10.7

SHA256 Checksums:

v2026.10.6

SHA256 Checksums:

v0.39.0

What's Changed

OpenTelemetry & LGTM

Other Changes

New Contributors

Configuration

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

`v2.6.4`

`v2026.10.7`

`v2026.10.6`

`v0.39.0`