fix(deps): update all dependencies by renovate[bot] · Pull Request #20 · ProverCoderAI/openapi-effect

renovate · 2026-02-21T13:44:04Z

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Type	Update
@biomejs/biome (source)	`^2.4.4` → `^2.6.3`	devDependencies	minor
@changesets/changelog-github (source)	`^0.5.2` → `^1.0.1`	devDependencies	major
@changesets/cli (source)	`^2.29.8` → `^3.0.3`	devDependencies	major
@eslint-community/eslint-plugin-eslint-comments	`^4.6.0` → `^4.8.1`	devDependencies	minor
@eslint/compat (source)	`2.0.2` → `2.1.1`	devDependencies	minor
@eslint/eslintrc	`3.3.3` → `3.3.7`	devDependencies	patch
@types/node (source)	`^24.10.13` → `^24.19.2`	devDependencies	minor
@typescript-eslint/eslint-plugin (source)	`^8.56.0` → `^8.72.0`	devDependencies	minor
@typescript-eslint/parser (source)	`^8.56.0` → `^8.72.0`	devDependencies	minor
@vitest/coverage-v8 (source)	`^4.0.18` → `^5.0.5`	devDependencies	major
@vitest/eslint-plugin	`^1.6.9` → `^1.6.28`	devDependencies	patch
actions/checkout	`v6` → `v7`	action	major
actions/setup-node	`v6` → `v7`	action	major
actions/upload-artifact	`v6` → `v7`	action	major
effect (source)	`^3.19.18` → `^4.0.6`	dependencies	major
eslint (source)	`^10.0.1` → `^10.13.0`	devDependencies	minor
eslint-import-resolver-typescript	`^4.4.4` → `^4.4.5`	devDependencies	patch
eslint-plugin-simple-import-sort	`^12.1.1` → `^14.0.0`	devDependencies	major
eslint-plugin-sonarjs (source)	`^4.0.0` → `^4.2.2`	devDependencies	minor
eslint-plugin-unicorn	`^63.0.0` → `^79.0.0`	devDependencies	major
globals	`^17.3.0` → `^17.13.0`	devDependencies	minor
jscpd (source)	`^4.0.8` → `^5.4.2`	devDependencies	major
node	`24.13.1` → `24.22.1`	uses-with	minor
pnpm (source)	`10.30.1` → `12.15.0`	packageManager	major
pnpm/action-setup	`v4` → `v6`	action	major
pnpm/action-setup	`v3` → `v6`	action	major
typescript (source)	`^5.9.3` → `^7.0.2`	devDependencies	major
typescript-eslint (source)	`^8.56.0` → `^8.72.0`	devDependencies	minor
vite (source)	`^7.3.1` → `^8.3.5`	devDependencies	major
vitest (source)	`^4.0.18` → `^5.0.5`	devDependencies	major

cc @skulidropek

Release Notes

biomejs/biome (@biomejs/biome)

`v2.6.3`

Compare Source

Patch Changes

#12275 807e616 Thanks @dyc3! - Added the new nursery rule noArraySortForMinMax, which reports sorting an array only to read its smallest or largest value. Use Math.min() or Math.max() instead.
```
const minimum = array.toSorted((a, b) => a - b)[0];
```
#12432 cf61682 Thanks @dyc3! - Added the nursery rule noBooleanSortComparator, which reports sort comparators that return a boolean instead of a number. For example, array.sort((a, b) => a > b) never puts the first item before the second, so the array isn't sorted correctly.
#12304 b4654c5 Thanks @dyc3! - Added the new nursery rule noEagerArrayMethodsInLoops, which reports .map() and .filter() calls in the header of for...of loops. These calls build a new array that is only used by the loop.
```
for (const name of users.map((user) => user.name)) {
  console.log(name);
}
```
#12121 66c3791 Thanks @dyc3! - Added the nursery rule noNewRequire, which disallows calling require with new, such as new require("app-header").
#12316 34b520d Thanks @dyc3! - Added the new nursery rule noObsoleteAttributes, which disallows obsolete attributes on HTML elements and suggests what to use instead.
```
<table bgcolor="#ffffff" cellpadding="5"></table>
```
#12258 cce2385 Thanks @dyc3! - Added the nursery rule noPathConcat, which disallows building file paths and URLs by joining strings to __dirname, __filename, import.meta.dirname, import.meta.filename, or import.meta.url.
```
const fullPath = __dirname + "/foo.js"; // reported
```
#12287 e12ad78 Thanks @dyc3! - Added the new nursery rule noPlaywrightNthMethods, which disallows selecting Playwright elements by position with first(), last(), and nth(). A test that relies on the position of an element can act on a different element when the page changes.
```
await page.locator("button").first().click();
```
#12343 62ad123 Thanks @vibbix! - Added the nursery rule noSelfNestedLayer, which disallows nesting a cascade layer inside a layer with the same name. Layer names inside an @layer block are relative to it, so the inner layer below creates the sublayer components.components instead of adding to components.
```
@layer components {
  @layer components {
    .button {
      color: red;
    }
  }
}
```
#12289 bbbd95d Thanks @dyc3! - Added the nursery rule noShortTimeValues, which reports CSS animation and transition times that are shorter than the configured minimum number of milliseconds. The rule does nothing until minimum is set.

For example, the following code is invalid when minimum is 100:
```
a {
  transition-duration: 80ms;
}
```
#12431 f748ec0 Thanks @dyc3! - Added the nursery rule noSvelteInternal, which disallows importing from svelte/internal and its submodules. These modules are private to Svelte and can change or disappear in any release.
```
import { get_current_component } from "svelte/internal";
```
#12270 8ae35c4 Thanks @dyc3! - Added the nursery rule noTanstackQueryRestDestructuring, which disallows rest destructuring and object spread on TanStack Query results. Both read every property of the result, so the component updates on every change to the query.
```
import { useQuery } from "@tanstack/react-query";

const { data, ...rest } = useQuery({ queryKey: ["todos"], queryFn: fetchTodos });
```
The rule belongs to the new tanstackQuery domain.
#12308 372af2a Thanks @dyc3! - Added the new nursery rule noUnreadableForOfExpression, which reports for...of and for await...of loops that go through the result of a complex expression instead of a variable, a property, or a short call.
```
for (const item of getItems(createArgument(seed))) {} // reported
```
#12422 0be8d10 Thanks @dyc3! - Added the new nursery rule noUnsafeReturn, which disallows returning a value typed as any from a function.
```
function parse(text: string) {
  return JSON.parse(text); // reported
}
```
#12311 8434c92 Thanks @dyc3! - Added the nursery rule noUselessSplice, which reports splice() calls that have a simpler alternative. For example, array.splice(0, 1) can be written as array.shift().
#12293 eaa4a2b Thanks @dyc3! - Added the nursery rule noVueUnusedEmitDeclarations, which reports events that a Vue component declares but never emits.

For example, the following component never emits close:
```
<script setup>
const emit = defineEmits(["change", "close"]);
emit("change");
</script>
```
#12386 f01ebb0 Thanks @dyc3! - Added the nursery rule noVueVTextVHtmlOnComponent, which disallows v-text and v-html on Vue components. These directives replace everything inside the component's root element instead of filling its slot.
```
<template>
  <MyComponent v-html="html"></MyComponent>
</template>
```
#12385 7bd38b7 Thanks @dyc3! - Added the new nursery rule noVueWatchAfterAwait, which disallows creating watchers after an await in a Vue component's setup() function. Vue doesn't stop these watchers when the component is removed. A watcher is allowed when the function it returns is stored, so that function can be called later to stop the watcher.
```
<script>
import { watch } from "vue";

export default {
  async setup() {
    await fetchUser();
    watch(source, () => {});
  },
};
</script>
```
#12286 50d2a4e Thanks @dyc3! - Added the nursery rule noZeroLengthUnit, which disallows units on zero lengths in CSS. Biome can remove the unit.
```
a {
  top: 0px;
}
```
#12300 ab2eb9e Thanks @dyc3! - Added the nursery rule useBlockStatementOverIife, which reports functions that are called immediately when a block statement can replace them. Biome can replace these functions with a block statement.

Invalid:
```
(() => {
    const value = getValue();
    run(value);
})();
```
#12421 1c2cac0 Thanks @dyc3! - Added the nursery rule useConsistentLightnessNotation, which enforces writing the lightness of lab(), lch(), oklab(), and oklch() colors as a percentage, or as a number with the notation option. For example, with the default options, oklch(0.85 0.17 88) is reported and can be fixed to oklch(85% 0.17 88).
#12224 fef7ed4 Thanks @dyc3! - Added the nursery rule useExpectToContain, which reports tests that compare the result of includes() to a boolean, and suggests using toContain() instead.
```
expect(fruits.includes("apple")).toBe(true);
```
#12299 0d5025d Thanks @dyc3! - Added the new nursery rule useIteratorZip, which reports for loops that use an index only to read the same position from several arrays. Such loops can use Iterator.zip() instead.
```
// reported
for (let index = 0; index < Math.min(names.length, scores.length); index++) {
  save(names[index], scores[index]);
}
```
#12298 a234d2f Thanks @dyc3! - Added the nursery rule useMathAbs, which reports manual absolute value calculations and range checks that can use Math.abs(). For example, value < 0 ? -value : value can be written as Math.abs(value), and value > limit || value < -limit can be written as Math.abs(value) > limit.
#12499 bd024cc Thanks @dyc3! - Added the nursery rule useMathTrunc, which requires Math.trunc() instead of bitwise operations or parseInt(String(x), 10) for removing the decimal part of a number. For example, const result = value | 0; and const result = ~~value; are now reported.
#12314 9e875a4 Thanks @dyc3! - Added the new nursery rule usePackageJsonValidCpu, which reports a cpu field in package.json that isn't an array of known processor types. The cpu field lists the processor types that the package supports.

For example, the rule reports the following package.json file because x86 isn't a processor type that package managers recognize:
```
{
  "name": "my-package",
  "cpu": ["x86"]
}
```
#12315 cb30544 Thanks @dyc3! - Added the nursery rule usePackageJsonValidEngines, which reports an invalid engines field in package.json. The field must be an object, and each of its values must be a non-empty string.

For example, the following engines field is reported because the version of node is a number:
```
{
    "engines": {
        "node": 24
    }
}
```
#12400 407604d Thanks @dyc3! - Added the nursery rule useVueComponentIs, which requires Vue <component> elements to bind the is attribute with :is or v-bind:is. Without it, Vue has no component to render.
```
<template>
  <component :is="currentView" />
</template>
```
#12337 c371520 Thanks @dyc3! - Added the nursery rule useVueToggleInsideTransition, which requires the element inside a Vue <Transition> to be shown and hidden with v-if or v-show. Without one of them, the element is always shown and the transition never plays.
```
<template>
  <Transition>
    <div>Content</div>
  </Transition>
</template>
```
#12387 64472e9 Thanks @dyc3! - Added the nursery rule useVueTypedRef, which reports ref() and shallowRef() calls in TypeScript that have no type argument and no initial value other than null or undefined. Without a type, TypeScript can't tell which values these refs are meant to hold.
```
import { ref } from "vue";

const count = ref();
```
#12423 bf1a55a Thanks @dyc3! - Added the nursery rule useVueVOnExact, which requires the .exact modifier on a v-on listener when another listener for the same event on the element needs more modifier keys, such as .ctrl. Without .exact, both listeners run when those keys are held down. The rule accepts the following code:
```
<template>
  <button @click.exact="select" @click.ctrl="open"></button>
</template>
```
#12418 208730e Thanks @latin-1! - Fixed #12417: useSortedProperties could produce invalid CSS when sorting properties without a final semicolon. Comments attached to reordered properties are preserved.
#12216 f2a3c71 Thanks @dyc3! - Added the new nursery rule noDanglingUnderscore, which disallows variable names, function names, and property accesses that start or end with an underscore.
```
const _count = 0; // reported
user._id; // reported
```
#12536 438997f Thanks @vidigoat! - Fixed the formatter removing the parentheses around an instantiation expression before +, -, <, >, >=, >> and >>>. TypeScript reads make<T> + y as make < T > +y, and make<T> >> y doesn't parse.
```
- x = make<T> + y;
+ x = (make<T>) + y;
- x = make<T> >> y;
+ x = (make<T>) >> y;
```
#12540 7d3e8a1 Thanks @vidigoat! - Fixed the formatter removing the parentheses around an instantiation expression before a non-null assertion or type arguments of a class heritage, which produced code that doesn't parse.
```
- const a = make<T>!;
+ const a = (make<T>)!;
- class D extends B<T><T> {}
+ class D extends (B<T>)<T> {}
```
#12496 09d89b9 Thanks @vidigoat! - Fixed the formatter removing the parentheses around binary, logical, type-cast and instantiation operands of an instantiation expression. The type arguments then applied to the last operand only, and a nested instantiation expression didn't parse.
```
- const x = a + b<T>;
+ const x = (a + b)<T>;
- const y = a as B<T>;
+ const y = (a as B)<T>;
- const z = f<A><B>;
+ const z = (f<A>)<B>;
```
#12526 dbcdab1 Thanks @dyc3! - Fixed #12524: the Markdown formatter no longer removes the blank line between a paragraph and the list that follows it. Removing it could change the document, because an ordered list that doesn't start at 1 can't interrupt a paragraph and became part of the paragraph text.
```
Steps:

3. three
4. four
```
#12509 470018b Thanks @dyc3! - Fixed #12507: the Markdown formatter no longer drops the > markers after an empty quote line when proseWrap is "always" or "never". Previously, the text after the empty line was moved out of the blockquote.
```
  > a
  >
- b
+ > b
```
#12598 5699601 Thanks @vidigoat! - Fixed the formatter removing the parentheses around the callee of a new expression when it contains a dynamic import() call, which produced code that doesn't parse.
```
- new import("foo").bar();
+ new (import("foo").bar)();
```
#12508 87d9e6b Thanks @dyc3! - Fixed #12502: noInvalidGridAreas now counts the cells in each row of grid-template-areas instead of comparing the length of the row text. Rows such as "a" "bb" are no longer reported, and rows such as "abc" "d e" are now reported.
#12530 7f467b2 Thanks @dyc3! - Fixed #12529: noUselessElse no longer reports an else clause when the if block ends with a switch statement that has no default clause. If no case matches, such a switch doesn't exit, so the else clause is needed.
#12511 d4ea663 Thanks @dyc3! - Fixed #12505: useDomNodeTextContent no longer reports innerText on values whose type annotation shows they aren't DOM nodes. The following code is now valid:
```
const Link = ({ innerText }: { innerText: string }) => <a>{innerText}</a>;
```
#12588 e262362 Thanks @ematipico! - Fixed noDescendingSpecificity to compare resolved nested selector targets. Biome no longer reports nested selectors that resolve to different targets, detects equivalent explicit and nested targets, and emits one diagnostic when a parent selector list expands the same nested selector multiple times.

For example, the following selectors are no longer reported because their final targets are .column and code, respectively:
```
.card {
  .column {
    :root[data-theme="dark"] & {}
  }

  code {
    :root[data-theme="dark"] & {}
  }
}
```
#12534 e59a324 Thanks @Netail! - Improved the diagnostics of noIdenticalTestTitle. Biome now reports one diagnostic per repeated title, pointing at the first occurrence and at every later occurrence, instead of one diagnostic per duplicate.
#12528 a3132dc Thanks @ff1451! - Fixed #12503: noUnknownProperty now checks SCSS nested properties by the name Sass emits for them. For example, radius in border: { radius: 4px; } is checked as border-radius and is no longer reported, while color in font: { color: red; } is checked as font-color and is now reported.
#12113 ec4eb2d Thanks @dyc3! - Added the nursery rule useConsistentUnicodeBom, which disallows a leading Unicode byte order mark by default and can require one with bom: "always". The rule supports JavaScript, TypeScript, JSON, CSS, GraphQL, HTML, and Markdown, provides a fix, and preserves the unicode-bom option during ESLint migration.

The following example is invalid by default because it starts with an invisible U+FEFF character:
```
const value = 1;
```
#12248 afbc81e Thanks @dyc3! - Added the nursery rule useReactNativeValidPlatformColors, which requires PlatformColor() and DynamicColorIOS() calls to use values written directly in the call, so React Native can optimize them.
```
import { PlatformColor } from "react-native";

const labelColor = "labelColor";
const color = PlatformColor(labelColor);
```
#12599 b62494a Thanks @dyc3! - Fixed #12532: checking the project root no longer applies files.includes exclusions to directories above the project.
#12578 6162922 Thanks @ematipico! - Fixed GraphQL parsing and formatting for executable descriptions and legacy fragment variables. Biome now formats inputs such as "Description" query { field } without panicking and removes insignificant commas consistently.
#12593 35c69ad Thanks @dyc3! - Fixed #12555: the default reporter now prints the command summary, the --max-diagnostics warning, and the skipped-fixes notice to stderr instead of stdout. Diagnostics already go to stderr, so the summary can no longer get mixed into the middle of a diagnostic when a tool reads the two streams separately.
#12415 9520907 Thanks @latin-1! - Fixed #12412: useSortedProperties now sorts properties inside @keyframes animations in CSS and SCSS.

`v2.6.2`

Compare Source

Minor Changes

#11479 5c60ba8 Thanks @nhedger! - Added a --git flag to biome init. The flag enables Git VCS integration and sets vcs.useIgnoreFile to true in the generated configuration, even when the command runs outside a Git repository.
#11742 3a1356d Thanks @Netail! - Added the biome migrate stylelint command. It imports a Stylelint configuration and its ignore settings into your Biome configuration, mapping Stylelint rules to their Biome equivalents. Pass --write to apply the changes, and --include-inspired or --include-nursery to migrate additional rules.
#12318 774b5b5 Thanks @Netail! - Added the new assist action useGraphqlSortedDefinitions, which sorts the named definitions of a GraphQL document, such as types, type extensions, directives, fragments, and operations.

Invalid:
```
type User {
  id: ID!
}

enum Role {
  ADMIN
  USER
}

directive @auth on FIELD_DEFINITION
```
#6886 3479d15 Thanks @christymcgrory! - biome rage now shows the resolved files.includes and files.ignoreUnknown configuration.
#11102 0874b7f Thanks @gameroman! - Added support for useTailwindSortedClasses rule in HTML-ish files.
#10711 40de5a0 Thanks @soconnor-seeq! - Adds a new resolutionKind option for object-syntax plugin entries.

This allows shared Biome configs in monorepos to load local Grit plugins from the package that declares them instead of resolving plugin paths from the consuming project.
```
{
  "plugins": [
    { "path": "./grit/no-debugger.grit", "resolutionKind": "config" },
    { "path": "local-plugin.grit", "resolutionKind": "project" },
    { "path": "local-plugin.grit" }
  ]
}
```
Use resolutionKind: "config" to resolve the plugin from the configuration file that declares it. Use resolutionKind: "project" to resolve the plugin from the consuming project. When omitted, resolutionKind defaults to project. This only affects plugin resolution; includes still apply to end-user project files as usual.
#11432 4befd08 Thanks @ematipico! - Added biome inspect config to show resolved configuration values and their origins as human-readable diagnostics, including matching overrides.

Configuration files can also extend other configurations up to ten levels deep. Repeated references to the same resolved file are ignored with an information diagnostic, while resolving multiple versions of one extended package produces an error.
#11477 ab05554 Thanks @nhedger! - Added automatic Git VCS integration when running biome init inside a Git repository, including from nested directories and Git worktrees. The generated configuration sets vcs.enabled and vcs.useIgnoreFile to true, with vcs.clientKind set to "git".
#11451 1ac4b09 Thanks @ematipico! - #### YAML is now supported

Added support for formatting YAML files, both .yaml and .yml extensions
#11432 4befd08 Thanks @ematipico! - Configuration files can now recursively extend local files and npm package configurations up to ten levels. Every repeated reference participates in the merge, while resolving multiple versions of one extended package produces an error.
#11713 ac6a640 Thanks @dyc3! - Added support for Grit range() patterns, addressing #8454. Plugins can filter syntax nodes by optional start_line, start_column, end_line, and end_column bounds.

For example, this pattern matches function calls contained entirely on line 2.
```
range(start_line=2, end_line=2) as $call where {
    $call <: call_expression()
}
```

#11244 0628b53 Thanks @ematipico! - Added the new CLI option --profile-type-inference to the commands lint and check.

The profiler is designed to track the execution time of internal queries and operations, group them by file, and sort them from the most expensive to the least expensive.

biome lint --profile-type-inference

profiler ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  i Type inference profile (Biome <version>)

  src/index.ts

    Requests (top 5 of 12 groups; 28 source records; 46 executions)
      1. Promise classification <- nursery/noFloatingPromises
      ...

    Queries (top 8 of 25 groups; 61 source records; 94 executions)
      1. Promises / infer_expression_is_promise
      ...

    Whole-module inference (top 1 of 1 group; 1 source record; 1 execution)
      1. Import depth limit
      ...

  68 files omitted.

  ℹ To show all the information, use the --verbose option. The output might be very verbose, so it's advised to analyze a single file.

  $ biome lint --profile-type-inference --verbose ./path/to/file.ts

Use --verbose to include detailed timings, attribution, breadth, and implementation references for the top source records in each file.

#12108 4fcb880 Thanks @ematipico! - Promoted 59 nursery rules to stable groups.

Correctness

Promoted the following rules to the correctness group with error severity. All of them are recommended:

Suspicious

Promoted the following rules to the suspicious group:

noLoopFunc
noJsxLeakedDollar
noReactStringRefs (recommended)
useScopedStyles (recommended)
noReactNativeDeepImports (recommended, error severity)
noDrizzleDeleteWithoutWhere (recommended, error severity)
noDrizzleUpdateWithoutWhere (recommended, error severity)
noConditionalExpect
useExpect
noIdenticalTestTitle (recommended)
noPlaywrightForceOption
noPlaywrightNetworkidle
noPlaywrightPagePause
noPlaywrightWaitForNavigation
noPlaywrightWaitForTimeout
noDuplicateSelectors
noEmptyObjectKeys
useBaseline
noUntrustedLicenses

Security

Promoted useIframeSandbox to the security group with error severity.

Performance

Promoted the recommended rule useDomNodeTextContent to the performance group with warning severity.

Complexity

Promoted the following rules to the complexity group:

useArraySome
useRegexpTest
noUnnecessaryTemplateExpression
noPlaywrightUselessAwait
noExcessiveSelectorClasses
useMathMinMax (recommended, warning severity)
noExcessiveNestedCallbacks

Style

Promoted the following rules to the style group with information severity:

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

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 was generated by Mend Renovate. View the repository job log.

coderabbitai · 2026-05-14T12:31:27Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: 2b203a0e-1d38-474c-9187-d98412e515df

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Last reviewed commit: 6898c52
Latest commit, not reviewed: f7bf54a

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

Walkthrough

Bump CI action versions, pin pnpm to 11.1.2 in root and app, and update Changesets plus many app dependencies/devDependencies (Effect stack, TypeScript tooling, linting, testing, and build tools).

Changes

Toolchain and dependency upgrades

Layer / File(s)	Summary
GitHub Actions versions `.github/actions/setup/action.yml`, `.github/workflows/checking-dependencies.yml`, `.github/workflows/snapshot.yml`	pnpm action bumped to `@v6` in composite and workflow; `actions/setup-node` Node input updated to `24.15.0`; artifact upload action bumped to `actions/upload-artifact@v7`.
pnpm version pins `package.json`, `packages/app/package.json`	Workspace and app `packageManager` updated from `pnpm@10.30.1` to `pnpm@11.1.2`.
Dependency and toolchain upgrades `package.json`, `packages/app/package.json`	Root Changesets packages (`@changesets/changelog-github`, `@changesets/cli`) bumped; app package `dependencies` and `devDependencies` refreshed (Effect packages, ts-morph, Biome/ESLint, TypeScript tooling, Vitest/Vite, etc.).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related issues

Dependency Dashboard effect-template#10: Overlaps pnpm/action-setup, pnpm pinning, and tooling/version updates.
Dependency Dashboard eslint-plugin-suggest-members#2: Matches workflow and pnpm/tooling bumps in CI and manifests.
Dependency Dashboard #1: Mirrors the same workflow and package.json version updates.
Dependency Dashboard dist-deps-prune#2: Contains similar dependency/version bump changes (pnpm, actions, packages).
Dependency Dashboard context-doc#5: Renovate-style workflow and package pin bumps align with that issue.
Dependency Dashboard effect-eslint-template#6: Shares pnpm and ESLint/Biome/tooling dependency updates.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description clearly documents the Renovate dependency, package manager, and GitHub Actions updates in the changeset.
Title check	✅ Passed	The title accurately identifies the pull request as a broad dependency update, including packages, tooling, and GitHub Actions.

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch renovate/all

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{🐇 I nudged a YAML line, made pnpm climb to eleven,
Actions hum a newer tune, workflows light as heaven.
Packages refreshed, linters wake and play,
Tests tiptoe cleaner paths, building through the day.
✨}

_{Comment @coderabbitai help to get the list of available commands.}

coderabbitai

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/actions/setup/action.yml:
- Line 13: The workflow currently uses a mutable tag "pnpm/action-setup@v6";
replace that with an immutable full commit SHA (40-hex) for pnpm/action-setup to
pin the action (e.g., "pnpm/action-setup@<full-commit-sha>"). Locate the "uses:
pnpm/action-setup@v6" entry in the action.yml and update it to the exact commit
SHA from the pnpm/action-setup repository, verify the SHA is full-length (40
characters) and that the workflow still runs correctly after the change.

In @.github/workflows/checking-dependencies.yml:
- Line 15: Replace the mutable tag reference "uses: pnpm/action-setup@v6" with
an immutable pin to the full commit SHA for the pnpm/action-setup action (e.g.,
"uses: pnpm/action-setup@<full-commit-sha>"); locate the occurrences of
"pnpm/action-setup@v6" in the workflow and update them to the corresponding
release commit SHA from the action's repository, then verify the workflow runs
successfully.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4cd2e52a-a23f-4849-8bc7-20b25e799703

📥 Commits

Reviewing files that changed from the base of the PR and between 6b3e168 and 373422e.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (5)

.github/actions/setup/action.yml
.github/workflows/checking-dependencies.yml
.github/workflows/snapshot.yml
package.json
packages/app/package.json

coderabbitai · 2026-05-14T12:34:25Z

  steps:
    - name: Install pnpm
-      uses: pnpm/action-setup@v3
+      uses: pnpm/action-setup@v6


⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash # Verify mutable action refs under .github (tag-based refs like `@v1/`@v6). # Expected: no matches after SHA pinning. rg -n --iglob '*.yml' --iglob '*.yaml' 'uses:\s*[^@[:space:]]+@v[0-9]+(\.[0-9]+){0,2}\b' .github

Repository: ProverCoderAI/openapi-effect

Length of output: 1009

Pin pnpm/action-setup to an immutable commit SHA.

Line 13 uses a mutable tag (@v6). Please pin to a full-length commit SHA to reduce supply-chain risk and avoid policy breaks in hardened org settings.

🔒 Suggested change

- uses: pnpm/action-setup@v6 + uses: pnpm/action-setup@<full-length-commit-sha> # v6.x

Reference: https://docs.github.com/actions/security-guides/security-hardening-for-github-actions

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/actions/setup/action.yml at line 13, The workflow currently uses a mutable tag "pnpm/action-setup@v6"; replace that with an immutable full commit SHA (40-hex) for pnpm/action-setup to pin the action (e.g., "pnpm/action-setup@<full-commit-sha>"). Locate the "uses: pnpm/action-setup@v6" entry in the action.yml and update it to the exact commit SHA from the pnpm/action-setup repository, verify the SHA is full-length (40 characters) and that the workflow still runs correctly after the change.

coderabbitai · 2026-05-14T12:34:25Z

    steps:
      - uses: actions/checkout@v6
-      - uses: pnpm/action-setup@v4
+      - uses: pnpm/action-setup@v6


⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash # Verify mutable action refs under .github (tag-based refs like `@v1/`@v6). # Expected: no matches after SHA pinning. rg -n --iglob '*.yml' --iglob '*.yaml' 'uses:\s*[^@[:space:]]+@v[0-9]+(\.[0-9]+){0,2}\b' .github

Repository: ProverCoderAI/openapi-effect

Length of output: 1009

Pin pnpm/action-setup to a commit SHA instead of a mutable tag.

Line 15 uses @v6, which is a mutable tag reference. Per GitHub's security hardening guidelines, action references should be pinned to full commit SHAs to ensure immutability and prevent unintended updates from tag rewrites.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/checking-dependencies.yml at line 15, Replace the mutable tag reference "uses: pnpm/action-setup@v6" with an immutable pin to the full commit SHA for the pnpm/action-setup action (e.g., "uses: pnpm/action-setup@<full-commit-sha>"); locate the occurrences of "pnpm/action-setup@v6" in the workflow and update them to the corresponding release commit SHA from the action's repository, then verify the workflow runs successfully.

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 6: The package.json currently sets "packageManager": "pnpm@11.1.2" but
pnpm v11 requires config and environment changes; run the recommended codemod
(pnpx codemod run pnpm-v10-to-v11) and then: move any settings under the
package.json "pnpm" field into pnpm-workspace.yaml, strip .npmrc to only
auth/registry entries, update .nvmrc and CI to Node.js 22+ to match pnpm v11,
rename any environment variables from npm_config_* to pnpm_config_ and manually
review remaining envs, and rename or invoke scripts named
clean/setup/deploy/rebuild using pnpm pm to avoid shadowing built-ins.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 78ded05a-1811-4eac-8349-84f29cb8618e

📥 Commits

Reviewing files that changed from the base of the PR and between 6898c52 and 57c74f4.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (5)

.github/actions/setup/action.yml
.github/workflows/checking-dependencies.yml
.github/workflows/snapshot.yml
package.json
packages/app/package.json

🚧 Files skipped from review as they are similar to previous changes (4)

.github/actions/setup/action.yml
.github/workflows/checking-dependencies.yml
.github/workflows/snapshot.yml
packages/app/package.json

coderabbitai · 2026-05-17T12:25:00Z

  "private": true,
  "description": "Monorepo workspace for effect-template",
-  "packageManager": "pnpm@10.30.1",
+  "packageManager": "pnpm@11.1.2",


⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

pnpm 11 breaking changes and migration guide

💡 Result:

pnpm 11 is a major release that introduces significant breaking changes, security-first defaults, and architectural improvements [1]. The official migration guide is available at https://pnpm.io/11.x/migration [2]. Key Breaking Changes and Migration Steps Configuration Changes pnpm 11 significantly changes how configuration is handled [3][1]: - Configuration is no longer read from the pnpm field in package.json; move these settings to pnpm-workspace.yaml [3][2]. -.npmrc files are now restricted to auth and registry settings only [3][1]. All other settings (e.g., hoist-pattern, node-linker) must be moved to pnpm-workspace.yaml using camelCase keys [3][2]. - npm_config_* environment variables are no longer supported; rename them to pnpm_config_* [3][1]. - pnpm no longer reads npm's global config at $PREFIX/etc/npmrc [1]. Dependency and Script Management - Build-dependency settings (onlyBuiltDependencies, neverBuiltDependencies, etc.) are consolidated into a single allowBuilds map in pnpm-workspace.yaml [3][1]. - Package manager strictness settings are collapsed into a single pmOnFail setting [3][2]. - Script names now shadow built-in commands [3]. If you have scripts named clean, setup, deploy, or rebuild, pnpm will execute your script instead of the built-in command; use pnpm pm to access the built-in version [3]. - pnpm install -g (with no arguments) is no longer supported; use pnpm add -g instead [3][1]. Environment and Infrastructure - Node.js 18, 19, 20, and 21 are no longer supported; Node.js 22+ is required [1]. - pnpm is now distributed as pure ESM [1]. - Global installs are now isolated using a global-virtual-store, preventing interference between global packages [1]. Security and New Features - Minimum Release Age: By default, pnpm 11 blocks the installation of package versions published within the last 24 hours to mitigate supply chain attacks [4][5][6]. - Exotic Subdependencies: pnpm 11 blocks dependencies resolved from non-standard sources (e.g., Git repositories or direct tarball URLs) by default [4][6]. - Native Publish: The npm CLI fallback for publishing has been removed in favor of a native implementation [1]. - Store Index: The store index has been migrated from a JSON-per-package format to a single SQLite database for improved performance [1][5]. Migration Tooling The pnpm team provides a codemod to automate many of these changes [2]. You can run it in your project directory: pnpx codemod run pnpm-v10-to-v11 [2] For changes that cannot be automated, such as environment variable updates, manual review is required [3][2].

Citations:

1: https://pnpm.io/blog/releases/11.0

2: https://pnpm.io/11.x/migration

3: https://pnpm.io/migration

4: https://gbhackers.com/pnpm-11-enables-default-release-age-guard/

5: https://cyberpress.org/pnpm-blocks-supply-attacks/

6: https://undercodenews.com/pnpm-11-reinvents-javascript-security-a-new-era-for-dependency-protection/

🌐 Web query:

pnpm 11.1.2 release notes and security advisories

💡 Result:

As of May 17, 2026, pnpm version 11.1.2 is the latest release [1]. Release Notes for pnpm 11.1.2 Specific release notes for version 11.1.2 were not explicitly detailed in the provided search results, as it is a very recent patch release [1]. However, it follows the major 11.1.0 and 11.1.1 releases, which introduced several significant features and fixes [2][3][4]: - New Commands: Added pnpm audit signatures (to verify ECDSA registry signatures), pnpm bugs (to open package bug trackers), and pnpm owner (to manage package owners) [3][4]. - Named Registries: Added support for installing packages from arbitrary named registries, including a built-in gh: prefix for the GitHub Packages npm registry [3][4]. - CI Improvements: Introduced the --no-runtime flag (config: runtime=false) to skip installing runtime entries (e.g., Node.js) in CI environments [3][4]. - Fixes: Version 11.1.1 included fixes for installability validation in workspace projects, resolved issues with pnpm add for named registries, and updated @zkochan/cmd-shim to improve compatibility with Git Bash on Windows [2]. Security Advisories There are no specific security advisories listed for version 11.1.2. Users should monitor the official pnpm GitHub Security Advisories page for any future disclosures [5]. Recent security-related updates in the pnpm 11 series include: - Minimum Release Age: pnpm 11 introduced a default Minimum Release Age of 24 hours (1440 minutes), which prevents the installation of newly published package versions to mitigate supply chain attacks [6][7][8]. - Enhanced Auditing: pnpm audit now queries the registry's bulk security advisories endpoint and filters by GitHub Advisory ID (GHSA) rather than CVE identifiers [9]. - Security Hardening: pnpm 11 requires Node.js 22+ and is distributed as pure ESM [10][11]. It also includes improved control over lifecycle scripts via the allowBuilds model [7][8]. For the most up-to-date information, always check the official pnpm releases page on GitHub and the security advisories section [12][5].

Citations:

1: https://www.npmjs.com/package/pnpm?activeTab=versions

2: https://github.com/pnpm/pnpm/releases/tag/v11.1.1

3: https://pnpm.io/blog/releases/11.1

4: https://newreleases.io/project/npm/pnpm/release/11.1.0

5: https://github.com/pnpm/pnpm/security/advisories

6: https://gbhackers.com/pnpm-11-enables-default-release-age-guard/

7: https://undercodenews.com/pnpm-11-reinvents-javascript-security-a-new-era-for-dependency-protection/

8: https://pnpm.io/supply-chain-security

9: https://pnpm.io/cli/audit

10: https://github.com/pnpm/pnpm/releases/tag/v11.0.0

11: https://pnpm.io/blog/releases/11.0

12: https://github.com/pnpm/pnpm/releases

Review pnpm 11 migration requirements before merging.

This major version upgrade introduces breaking changes that require configuration updates and environment adjustments:

Configuration files: Settings in package.json's pnpm field must move to pnpm-workspace.yaml. Update .npmrc to contain only auth and registry settings.

Node.js requirement: pnpm 11 requires Node.js 22+. Verify your project's .nvmrc and CI configuration specify a compatible version.

Environment variables: Any npm_config_* variables must be renamed to pnpm_config_*.

Script behavior: Scripts named clean, setup, deploy, or rebuild now shadow built-in commands; use pnpm pm to access built-in versions.

Run the migration codemod to automate configuration changes:

pnpx codemod run pnpm-v10-to-v11

Refer to https://pnpm.io/11.x/migration for the complete migration guide. Manual review is needed for environment variable updates that the codemod cannot automate.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@package.json` at line 6, The package.json currently sets "packageManager": "pnpm@11.1.2" but pnpm v11 requires config and environment changes; run the recommended codemod (pnpx codemod run pnpm-v10-to-v11) and then: move any settings under the package.json "pnpm" field into pnpm-workspace.yaml, strip .npmrc to only auth/registry entries, update .nvmrc and CI to Node.js 22+ to match pnpm v11, rename any environment variables from npm_config_* to pnpm_config_ and manually review remaining envs, and rename or invoke scripts named clean/setup/deploy/rebuild using pnpm pm to avoid shadowing built-ins.

skulidropek · 2026-06-19T19:15:56Z

Надо смержить сюда main ветку и исправить все ошибки в CI/CD что бы код был с актуальными библиотеками

konard · 2026-06-19T19:17:53Z

🤖 AI Work Session Started

Starting automated work session at 2026-06-19T19:17:51.406Z

The PR has been converted to draft mode while work is in progress.

This comment marks the beginning of an AI work session. Please wait for the session to finish, and provide your feedback.

konard · 2026-06-19T19:58:09Z

Update: the CI/CD fix is implemented and verified, but I cannot push it directly to this PR head branch.

Blocker:

PR fix(deps): update all dependencies #20 head is ProverCoderAI/openapi-effect:renovate/all.
Current GitHub credentials are konard and git push upstream renovate/all fails with 403 Permission to ProverCoderAI/openapi-effect.git denied to konard.

Prepared fix:

Commit: b16eac4b7948745fcd49d07e270b92f77b0ccb7d (fix(ci): adapt renovate update to pnpm 11)
Branch with the commit: konard/ProverCoderAI-openapi-effect:renovate/all

What the fix covers:

merged main into renovate/all locally;
moved pnpm 11 config from package.json#pnpm into pnpm-workspace.yaml and kept release-age policy with exact excludes;
pinned pnpm/action-setup to full SHA 0ebf47130e4866e96fce0953f49152a61190b271 (v6.0.9);
updated CI Node runtime to 24.17.0 so pnpm 11 can load node:sqlite;
fixed TypeScript 6/lint fallout while preserving legacy public aliases;
added consumer compile proof for the legacy serializer aliases.

Verification:

Local: pnpm install --frozen-lockfile && pnpm check && pnpm build && pnpm lint:effect && pnpm test && pnpm --filter @prover-coder-ai/openapi-effect test:consumer && pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent passed with Node 24.17.0 / pnpm 11.8.0.
Fork CI Check passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27845776274
Fork CI Checking Dependencies passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27845776279

Needed human action: either grant/push access to ProverCoderAI/openapi-effect:renovate/all, or cherry-pick b16eac4b7948745fcd49d07e270b92f77b0ccb7d from the fork branch into the PR head branch.

konard · 2026-06-19T19:59:20Z

🤖 Solution Draft Log

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $21.304392

📊 Context and tokens usage:

508.9K / 200K (254%) input tokens, 68.4K / 128K (53%) output tokens

Total: (508.9K + 13.1M cached) input tokens, 68.4K output tokens, $21.304392 cost

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Thinking level: max (~31999 tokens)
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (75696KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:01:31Z

🔄 Auto-restart triggered (iteration 1)

Reason: CI failures detected

Starting new session to address the issues.

Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations.

konard · 2026-06-19T20:09:42Z

Rechecked the failing CI/CD status in this restart session.

Findings:

Latest upstream PR runs are still for old SHA 48c4a8472fb0d70d3d48c14f5963a2d421a90ec7 from 2026-06-19T13:11:52Z.
Logs saved locally during investigation show the failures are from pnpm 11 running on Node 20.16.0 / 22.12.0 and from pnpm 11 ignoring package.json#pnpm, causing minimumReleaseAge violations.
The prepared fix commit is still b16eac4b7948745fcd49d07e270b92f77b0ccb7d on konard/ProverCoderAI-openapi-effect:renovate/all.

Verification repeated locally with Node 24.17.0 and pnpm 11.8.0:

pnpm install --frozen-lockfile
pnpm check
pnpm build
pnpm lint:effect
pnpm lint
pnpm test
pnpm --filter @prover-coder-ai/openapi-effect test:consumer
pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent
snapshot fallback artifact check via npm pack

Fork CI also has successful runs for b16eac4: Check 27845776274, Checking Dependencies 27845776279.

Remaining blocker is repository permissions, not code: git push upstream renovate/all still fails with 403 Permission to ProverCoderAI/openapi-effect.git denied to konard. Please either grant push access to ProverCoderAI/openapi-effect:renovate/all or cherry-pick/push b16eac4b7948745fcd49d07e270b92f77b0ccb7d from the fork branch into the upstream PR head branch.

konard · 2026-06-19T20:11:08Z

🔄 Auto-restart-until-mergeable Log (iteration 1)

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $4.197492
Token usage: 93,621 input, 17,194 output, 5,819 reasoning, 2,487,552 cache read

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (96784KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:13:21Z

🔄 Auto-restart triggered (iteration 2)

Reason: CI failures detected

Starting new session to address the issues.

Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations.

konard · 2026-06-19T20:22:22Z

Rechecked and updated the prepared fix in this restart session.

Current prepared commit:

b52bed11666e71930f1d563062826936f36fd5f3 on konard/ProverCoderAI-openapi-effect:renovate/all
This includes the earlier CI/pnpm 11 fix plus a small follow-up commit fix(app): satisfy strict type lint example so lint:types also passes.

Root causes confirmed from upstream CI logs for old SHA 48c4a8472fb0d70d3d48c14f5963a2d421a90ec7:

Check/Snapshot: pnpm 11 ran under an old Node runtime and failed on node:sqlite / Node >= 22.13 requirement.
dist-deps-prune: pnpm 11 minimum release age policy rejected fresh lockfile entries.

Verification on current SHA b52bed1:

Local with Node 24.17.0 and pnpm 11.8.0: pnpm install --frozen-lockfile, pnpm check, pnpm build, pnpm lint, pnpm lint:effect, pnpm test, pnpm lint:tests, pnpm --filter @prover-coder-ai/openapi-effect lint:types, pnpm --filter @prover-coder-ai/openapi-effect test:consumer, pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent, and package pack check all passed.
Fork CI Check passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27846721442
Fork CI Checking Dependencies passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27846721454
Fork Snapshot is skipped by the workflow owner guard (github.repository_owner == 'ProverCoderAI'); the equivalent local pnpm build plus fallback npm pack artifact path passed.

Remaining blocker is repository permission, not code. git push upstream renovate/all still fails with:

remote: Permission to ProverCoderAI/openapi-effect.git denied to konard.
fatal: unable to access 'https://github.com/ProverCoderAI/openapi-effect.git/': The requested URL returned error: 403

Needed maintainer action: push/cherry-pick b52bed11666e71930f1d563062826936f36fd5f3 from the fork branch into ProverCoderAI/openapi-effect:renovate/all. Until that happens, PR #20 remains on the old upstream head SHA 48c4a8472fb0d70d3d48c14f5963a2d421a90ec7 and will keep showing stale failing checks.

konard · 2026-06-19T20:24:34Z

🔄 Auto-restart-until-mergeable Log (iteration 2)

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $4.788024
Token usage: 95,677 input, 18,030 output, 5,431 reasoning, 3,019,904 cache read

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (2 chunks) (116514KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:26:47Z

🔄 Auto-restart triggered (iteration 3)

Reason: CI failures detected

Starting new session to address the issues.

Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations.

konard · 2026-06-19T20:33:49Z

Restart iteration 3 rechecked the prepared CI fix.

Current verified head:

b52bed11666e71930f1d563062826936f36fd5f3 on konard/ProverCoderAI-openapi-effect:renovate/all
Local branch includes upstream/main via merge commit f43684a.
PR fix(deps): update all dependencies #20 still points to ProverCoderAI/openapi-effect:renovate/all@48c4a8472fb0d70d3d48c14f5963a2d421a90ec7, so its failing checks are stale for the old head.

Fresh upstream CI logs downloaded in this session confirm old-head root causes:

Check: pnpm 11 under Node 20.16.0 fails on node:sqlite / Node >= 22.13 requirement.
Snapshot: pnpm 11 under Node 22.12.0 fails the Node >= 22.13 requirement.
Checking Dependencies: pnpm 11 ignores package.json#pnpm and then fails minimumReleaseAge for the refreshed lockfile entries.

Verification repeated on b52bed1 with Node 24.17.0 and pnpm 11.8.0:

pnpm install --frozen-lockfile
pnpm check
pnpm build
pnpm lint
pnpm lint:effect
pnpm test
pnpm lint:tests
pnpm --filter @prover-coder-ai/openapi-effect lint:types
pnpm --filter @prover-coder-ai/openapi-effect test:consumer
pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent
snapshot fallback npm pack artifact path

Push blocker remains external:
git push upstream HEAD:renovate/all fails with 403 Permission to ProverCoderAI/openapi-effect.git denied to konard.

Needed maintainer action: push or cherry-pick b52bed11666e71930f1d563062826936f36fd5f3 from the fork branch into ProverCoderAI/openapi-effect:renovate/all.

konard · 2026-06-19T20:35:31Z

🔄 Auto-restart-until-mergeable Log (iteration 3)

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $4.433867
Token usage: 92,361 input, 16,725 output, 5,362 reasoning, 2,757,632 cache read

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (2 chunks) (139990KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:37:44Z

🔄 Auto-restart triggered (iteration 4)

Reason: CI failures detected

Starting new session to address the issues.

Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations.

konard · 2026-06-19T20:44:12Z

Restart iteration 4 rechecked the CI/CD fix.

Current verified head:

b52bed11666e71930f1d563062826936f36fd5f3 on konard/ProverCoderAI-openapi-effect:renovate/all
upstream/main is merged into this branch.
PR fix(deps): update all dependencies #20 upstream head is still ProverCoderAI/openapi-effect:renovate/all@48c4a8472fb0d70d3d48c14f5963a2d421a90ec7, so the visible failing checks are still for the old head.

Fresh upstream logs downloaded in this session confirm the old-head failures:

Check: pnpm 11 runs under Node 20.16.0 and fails on node:sqlite / Node >= 22.13.
Snapshot: pnpm 11 runs under Node 22.12.0 and fails the Node >= 22.13 requirement.
Checking Dependencies: pnpm 11 rejects fresh lockfile entries through minimumReleaseAge.

Verification repeated locally on b52bed1 with Node 24.17.0 and pnpm 11.8.0:

pnpm install --frozen-lockfile
pnpm check
pnpm build
pnpm lint
pnpm lint:effect
pnpm test
pnpm lint:tests
pnpm --filter @prover-coder-ai/openapi-effect lint:types
pnpm --filter @prover-coder-ai/openapi-effect test:consumer
pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent
snapshot fallback artifact check via npm pack

Push status:

git push origin HEAD:renovate/all: up to date.
git push upstream HEAD:renovate/all: blocked with 403 Permission to ProverCoderAI/openapi-effect.git denied to konard.

Needed maintainer action: push or cherry-pick b52bed11666e71930f1d563062826936f36fd5f3 from konard/ProverCoderAI-openapi-effect:renovate/all into ProverCoderAI/openapi-effect:renovate/all. Until then PR #20 cannot receive fresh CI for the verified fix.

konard · 2026-06-19T20:45:53Z

🔄 Auto-restart-until-mergeable Log (iteration 4)

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $4.654120
Token usage: 127,152 input, 17,640 output, 5,582 reasoning, 2,588,800 cache read

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (2 chunks) (154923KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:48:07Z

🔄 Auto-restart triggered (iteration 5)

Reason: CI failures detected

Starting new session to address the issues.

Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations.

konard · 2026-06-19T20:54:43Z

Restart iteration 5 rechecked the CI/CD failures and the prepared fix.

Current verified fix:

b52bed11666e71930f1d563062826936f36fd5f3 on konard/ProverCoderAI-openapi-effect:renovate/all
This branch includes upstream/main and has origin/renovate/all up to date.

Fresh upstream CI status:

PR fix(deps): update all dependencies #20 still points to ProverCoderAI/openapi-effect:renovate/all@48c4a8472fb0d70d3d48c14f5963a2d421a90ec7.
Latest upstream runs are still from 2026-06-19T13:11:52Z for that old SHA:
- Check 27827776411: failure
- Checking Dependencies 27827776440: failure
- Snapshot 27827776423: failure

Root causes confirmed from downloaded upstream logs:

Check jobs (Build, Types, Lint, Lint Effect-TS, Test) fail before project code because pnpm 11 runs under Node 20.16.0 and errors with No such built-in module: node:sqlite / Node >= 22.13 requirement.
Snapshot fails for the same pnpm 11 runtime requirement under Node 22.12.0.
dist-deps-prune fails with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION for effect@3.21.4, eslint-plugin-sonarjs@4.1.0, and eslint-plugin-unicorn@68.0.0.

Verification repeated locally on b52bed1 with Node 24.17.0 and pnpm 11.8.0:

pnpm install --frozen-lockfile
pnpm check
pnpm build
pnpm lint
pnpm lint:effect
pnpm test
pnpm lint:tests
pnpm --filter @prover-coder-ai/openapi-effect lint:types
pnpm --filter @prover-coder-ai/openapi-effect test:consumer
pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent
snapshot fallback artifact path via npm pack

Fork CI on b52bed1:

Check passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27846721442
Checking Dependencies passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27846721454
Snapshot skipped by the workflow owner guard (github.repository_owner == 'ProverCoderAI'); the equivalent local build plus fallback pack path passed.

Push status:

git push origin HEAD:renovate/all: up to date.
git push upstream HEAD:renovate/all: blocked with 403 Permission to ProverCoderAI/openapi-effect.git denied to konard.

Needed maintainer action: push or cherry-pick b52bed11666e71930f1d563062826936f36fd5f3 from konard/ProverCoderAI-openapi-effect:renovate/all into ProverCoderAI/openapi-effect:renovate/all. Until that upstream PR head moves off 48c4a84, the visible PR checks remain stale failures for the old commit.

konard · 2026-06-19T20:56:07Z

🔄 Auto-restart-until-mergeable Log (iteration 5)

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $4.888533
Token usage: 166,658 input, 16,101 output, 4,054 reasoning, 2,497,408 cache read

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (2 chunks) (177139KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:58:19Z

⚠️ Auto-restart limit reached

Hive Mind stopped auto-restart-until-mergeable after 5 restart iterations.

Configured limit: 5
Remaining reason: CI failures detected

No further AI sessions will be started automatically for this run. Please review the remaining blockers manually or rerun with a higher --auto-restart-max-iterations value.

Auto-restart-until-mergeable stopped by the safety limit.

konard · 2026-06-19T20:58:26Z

🤖 AI Work Session Completed

Work session ended at 2026-06-19T20:58:19.771Z

The PR will be converted back to ready for review.

This comment marks the end of an AI work session. New comments after this time will be considered as feedback.

renovate Bot assigned skulidropek Feb 21, 2026

renovate Bot requested a review from skulidropek February 21, 2026 13:44

renovate Bot force-pushed the renovate/all branch from 61f06bc to 4c58bf8 Compare February 23, 2026 22:47

renovate Bot changed the title ~~fix(deps): update dependency effect to ^3.19.19~~ fix(deps): update all dependencies Feb 23, 2026

renovate Bot force-pushed the renovate/all branch 9 times, most recently from 52aba09 to 16d549f Compare March 2, 2026 17:40

renovate Bot force-pushed the renovate/all branch 10 times, most recently from f240877 to 3c2e51f Compare March 9, 2026 23:06

renovate Bot force-pushed the renovate/all branch 7 times, most recently from 9456c54 to 0ff8d9f Compare March 17, 2026 14:38

renovate Bot force-pushed the renovate/all branch 5 times, most recently from 6ff8486 to 4c77644 Compare April 24, 2026 02:39

coderabbitai Bot requested changes May 14, 2026

View reviewed changes

coderabbitai Bot requested changes May 17, 2026

View reviewed changes

fix(deps): update all dependencies

f7bf54a

Conversation

renovate Bot commented Feb 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v2.6.3

Patch Changes

v2.6.2

Minor Changes

Correctness

Suspicious

Security

Performance

Complexity

Style

Configuration

Uh oh!

coderabbitai Bot commented May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Reviews paused

Changes

Estimated code review effort

Possibly related issues

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot May 17, 2026

Choose a reason for hiding this comment

Uh oh!

skulidropek commented Jun 19, 2026

Uh oh!

konard commented Jun 19, 2026

Uh oh!

konard commented Jun 19, 2026

Uh oh!

konard commented Jun 19, 2026

🤖 Solution Draft Log

💰 Cost estimation:

📊 Context and tokens usage:

🤖 Models used:

📎 Log file uploaded as Repository (75696KB)

Uh oh!

konard commented Jun 19, 2026

🔄 Auto-restart triggered (iteration 1)

Uh oh!

konard commented Jun 19, 2026

Uh oh!

konard commented Jun 19, 2026

🔄 Auto-restart-until-mergeable Log (iteration 1)

💰 Cost estimation:

🤖 Models used:

📎 Log file uploaded as Repository (96784KB)

Uh oh!

konard commented Jun 19, 2026

🔄 Auto-restart triggered (iteration 2)

Uh oh!

konard commented Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

konard commented Jun 19, 2026

🔄 Auto-restart-until-mergeable Log (iteration 2)

💰 Cost estimation:

🤖 Models used:

📎 Log file uploaded as Repository (2 chunks) (116514KB)

Uh oh!

konard commented Jun 19, 2026

🔄 Auto-restart triggered (iteration 3)

Uh oh!

konard commented Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

renovate Bot commented Feb 21, 2026 •

edited

Loading

`v2.6.3`

`v2.6.2`

coderabbitai Bot commented May 14, 2026 •

edited

Loading

konard commented Jun 19, 2026 •

edited

Loading

konard commented Jun 19, 2026 •

edited

Loading